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
TASK: Within collection require packages as self.version #3034
Labels
Comments
kdambekalns
changed the title
TASK: With in collection require packages as self.version
TASK: Within collection require packages as self.version
May 3, 2023
Closed
1 task
kdambekalns
added a commit
to kdambekalns/flow-development-collection
that referenced
this issue
May 3, 2023
kdambekalns
added a commit
to kdambekalns/flow-development-collection
that referenced
this issue
May 3, 2023
6 tasks
neos-bot
pushed a commit
to neos/flow
that referenced
this issue
Jun 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Description
To ensure packages released together from the same mono-repository are always installed in matching versions, those should require each other as
self.version
, possible since Composer 2.2.8 (see composer/composer#10593).This would provide and eaasy way to avoid
*
constraints that otherwise might lead to unintentional upgrades (or downgrades) of packages.As an added bonus it would make it easier to spot failed mono-repo splits.
Possible Solution
No response
The text was updated successfully, but these errors were encountered: