-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update drupal/upgrade_status from 4.0.0 to 4.3.1 #145
Open
violinist-bot
wants to merge
1
commit into
balsama:main
Choose a base branch
from
violinist-dev:drupalupgradestatus400431
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update drupal/upgrade_status from 4.0.0 to 4.3.1 #145
violinist-bot
wants to merge
1
commit into
balsama:main
from
violinist-dev:drupalupgradestatus400431
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
4 times, most recently
from
June 2, 2024 22:04
54497d8
to
9296160
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
from
June 6, 2024 14:21
9296160
to
6eff605
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
2 times, most recently
from
June 19, 2024 22:21
4abfc83
to
f563575
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
2 times, most recently
from
July 1, 2024 16:17
ca85ea1
to
7d05f95
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
from
July 6, 2024 22:22
7d05f95
to
468462f
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
2 times, most recently
from
July 26, 2024 15:18
48c35a0
to
ded30af
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
2 times, most recently
from
August 8, 2024 12:20
8a54854
to
bdedefe
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
2 times, most recently
from
August 21, 2024 16:23
5ddb6b7
to
2a703de
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
3 times, most recently
from
August 31, 2024 07:37
b5ddd3d
to
9b436e6
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
5 times, most recently
from
September 9, 2024 22:12
306c4ab
to
a9df696
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
2 times, most recently
from
September 17, 2024 22:26
d26f403
to
8f93c18
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
3 times, most recently
from
September 22, 2024 22:22
6b86b46
to
ec4037b
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
from
September 26, 2024 08:57
ec4037b
to
239e2cc
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
2 times, most recently
from
September 29, 2024 22:11
524b6b4
to
1e40242
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
from
October 6, 2024 17:20
1e40242
to
e95fa5a
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
2 times, most recently
from
October 18, 2024 13:25
2d9f808
to
5893b2a
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
from
October 27, 2024 23:09
5893b2a
to
b8665a9
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
3 times, most recently
from
November 11, 2024 18:22
4fc3e5d
to
52eebaf
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
from
November 17, 2024 15:24
52eebaf
to
3f82e2b
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
2 times, most recently
from
November 28, 2024 22:23
6e559c0
to
f36c971
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
from
December 17, 2024 22:59
f36c971
to
4726768
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
2 times, most recently
from
January 5, 2025 23:13
b04eaf6
to
5c0a27d
Compare
violinist-bot
force-pushed
the
drupalupgradestatus400431
branch
from
January 21, 2025 16:08
5c0a27d
to
d2c5f46
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you have a high test coverage index, and your tests for this pull request are passing, it should be both safe and recommended to merge this update.
Updated packages
Some times an update also needs new or updated dependencies to be installed. Even if this branch is for updating one dependency, it might contain other installs or updates. All of the updates in this branch can be found here:
Release notes
Here are the release notes for all versions released between your current running version, and the version this PR updates the package to.
List of release notes
Changed files
Here is a list of changed files between the version you use, and the version this pull request updates to:
List of changed files
Changelog
Here is a list of changes between the version you use, and the version this pull request updates to:
Issue #3444271 by Gábor Hojtsy: Return real line numbers in info file report
Issue #3227079 by RoSk0, bartlangelaan, Gábor Hojtsy, kim.pepper: Support generating Code Quality JSON reports (for GitLab CI integration)
Issue #3354706 by Gábor Hojtsy, vacho, mandclu, alison, henokmikre, andrewmacpherson: PHPStan 'No files found to analyse' is considered a problem, even though it may be valid for certain extensions
Issue #3441737 by Gábor Hojtsy, bbrala: Update rector coverage list based on Deprecation Status scripts
Issue #3352605 by Gábor Hojtsy, loze, joseph.olstad: Warning in TwigDeprecationAnalyzer when the error caught is not in a twig file
Issue #3421454 by Gábor Hojtsy, ressa, risforrocket: Keep module compatible with nikic/php-parser v4, while adding v5 support
Issue #3421454 by Gábor Hojtsy, ressa, risforrocket: Module incompatibility with nikic/php-parser v5.0.0
Issue #3307587 by Gábor Hojtsy, estherp, Pasqualle, mpaulo, mglaman, saschaeggi: Massive Upgrade Status CSS cleanup to be compatible with more admin themes
Issue #3175323 by Gábor Hojtsy, lhridley, mglaman, andypost, moshe weitzman: The analyze command should report proper exit code
Issue #3423014 by Gábor Hojtsy: Drupal 11 system requirements are now defined, check for them in Upgrade Status
Issue #3338745 by Gábor Hojtsy, wells, joelpittet, randallquesadaa, leymannx: CSS files are found in node_modules and other third party directories
Issue #3419115 by Gábor Hojtsy, Grimreaper, nsavitsky, PapaGrande, rishabjasrotia, samir_shukla, DrupalDope: Dependency tree of mathieuviossat/arraytotexttable causes compatibility issues with PHP 8.2 and 8.3
Issue #3392667 by lamp5, Gábor Hojtsy: Add core/drupal.dialog.ajax as a library dependency
Issue #3418122 by MacSim, Gábor Hojtsy: Drush 12 compatibility
Issue #3330000 by lostcarpark: Consider adding a Project Logo
Issue #3409447 by gorkagr: Paran used instead of Param in ProjectCollector class
Should use needs instead of dependencies.
Only use one version of the artifacts for the linting jobs, rather than all
Issue #3403478 by Gábor Hojtsy: Resolve stylelint issues
Issue #3403771 by Gábor Hojtsy: Info and composer metadata checking is outdated
Issue #3403194 by marvil07, Gábor Hojtsy: Adopt gitlab CI for testing
Issue #3403192 by Gábor Hojtsy: Update rectorable message list to drupal-rector 0.18.1
Issue #3368554 by akshay.singh, arti_parmar, mrinalini9, Gábor Hojtsy, apaderno: Remove unused variables
Issue #3324201 by abramm, prudloff: CSSDeprecationAnalyzer::getAllCSSFiles() returns directories with a name that ends in ".css"
Issue #3332142 by Shubham Rathore, thakurnishant_06, apaderno, Gábor Hojtsy: Update README.md file according to README.md template
Issue #3366782 by Gábor Hojtsy: Stop suggesting Upgrade Rector, that is not well maintained, people should use drupal-rector
Working with this branch
If you find you need to update the codebase to be able to merge this branch (for example update some tests or rebuild some assets), please note that violinist will force push to this branch to keep it up to date. This means you should not work on this branch directly, since you might lose your work. Read more about branches created by violinist.io here.
This is an automated pull request from Violinist: Continuously and automatically monitor and update your composer dependencies. Have ideas on how to improve this message? All violinist messages are open-source, and can be improved here.