chore: do not propagate composer update to bins#980
Closed
ChristophWurst wants to merge 0 commit intomasterfrom
Closed
chore: do not propagate composer update to bins#980ChristophWurst wants to merge 0 commit intomasterfrom
ChristophWurst wants to merge 0 commit intomasterfrom
Conversation
marcelklehr
approved these changes
Apr 17, 2025
512dae7 to
3bffb77
Compare
auto-merge was automatically disabled
November 12, 2025 09:32
Pull request was closed
3bffb77 to
f5312aa
Compare
Member
Author
|
This was replaced by c1492fa |
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
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.
Running
composer update <package>in the root shouldn't propagate to the composer bins.How to test
Run
composer update voku/portable-utf8master: bins update all packages that can be updated 😠
here: bins stay the same, root updates the one specific package, if possible 😀