-
-
Notifications
You must be signed in to change notification settings - Fork 0
Updated contrib dependencies and applied the 'drupal/ai' security release. #324
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
Merged
+67
−68
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All five constraint changes in this file are mechanical:
config.bump-after-updateis enabled, socomposer updatetightened each direct dependency's floor to the version it just installed. None of them is a deliberate policy change, and no dependency was added or removed.composer validate --strictpasses andcomposer normalizereports the file already normalized.Routine, per line:
drupal/moderated_content_bulk_publish^2.0to^2.0.53(this line). Patch release; the constraint gains a floor it did not previously state.drush/drush^13.7.6to^13.7.7- fixes inconsistentselfversusstaticuse inAutowireTrait, Issue #6470 Fixes inconsistent use of self vs static in AutowireTrait drush-ops/drush#6476. Nothing inweb/modules/customsubclasses it.drevops/behat-steps^3.14.1to^3.14.2- expands fixture path resolution for file and image fields in subdirectories, [#760] Expanded fixture paths for file and image fields in subdirectories. behat-steps#764. No step definitions were renamed or removed, so the 41 feature files undertests/behat/featuresneed no migration;ahoy lintandahoy test-unitpass unchanged.phpstan/phpstan^2.2.10to^2.2.13- three patch releases.ahoy lint-bereports[OK] No errorsagainstphpstan.neon, so no new findings on this codebase.The one that carries a real decision:
palantirnet/drupal-rector^1.1.2to^1.1.3. Its only functional change is adding"conflict": {"rector/rector": ">=2.6.2"}(fix: conflict with rector/rector >=2.6.2 (#420) palantirnet/drupal-rector#421), because rector 2.6.2 removedPHPUnitSetListwhile theDrupal8/Drupal9/Drupal10set lists still reference it (rector 2.6.2+ breaks Drupal*SetList because PHPUnitSetList was removed palantirnet/drupal-rector#420). Composer therefore resolvesrector/rectordown to 2.6.1 in the lock. That downgrade is not reachable-defect-driven here: this site is on core 11.4, andDrupalSetProvideronly loads the sets whose version core satisfies, so only the 11.x sets load and none of those referencedPHPUnitSetList. What it does change is where the ceiling lives - this project had been holding rector at 2.6.2 incomposer.lockalone, and that hold is now declared upstream by the constraint instead.Rector\Set\ValueObject\ComposerTriggeredSetandRector\Set\Contract\SetProviderInterfaceboth still exist in 2.6.1, sorector.phpresolves unchanged and[OK] Rector is done!locally.Not visible in this file: the security fix in this PR is
drupal/ai1.4.7 to 1.4.8, which closes SA-CONTRIB-2026-119 (XSS, CVE-2026-84911) and SA-CONTRIB-2026-120 (access bypass, CVE-2026-84912).drupal/aiis transitive - it arrives throughdrupal/ai_image_alt_text,drupal/ai_provider_openaianddrupal/gemini_provider- so it has no constraint line here and moves only incomposer.lock.composer auditreported both advisories against the pre-update lock and reports none against this one.