Skip to content
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

Open
1 task done
kdambekalns opened this issue May 3, 2023 · 1 comment
Open
1 task done

TASK: Within collection require packages as self.version #3034

kdambekalns opened this issue May 3, 2023 · 1 comment
Assignees
Labels

Comments

@kdambekalns
Copy link
Member

Is there an existing issue for this?

  • I have searched the existing issues

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

@kdambekalns kdambekalns self-assigned this May 3, 2023
@kdambekalns
Copy link
Member Author

kdambekalns commented May 3, 2023

Related: neos/neos-development-collection#4257

@kdambekalns kdambekalns changed the title TASK: With in collection require packages as self.version TASK: Within collection require packages as self.version May 3, 2023
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
@kitsunet kitsunet reopened this Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants