TASK: Within collection require packages as self.version #4257
Comments
kdambekalns
changed the title
1 task
12 tasks
neos-bot
pushed a commit
to neos/cli-setup
that referenced
this issue
May 31, 2023
neos-bot
pushed a commit
to neos/fusion-afx
that referenced
this issue
May 31, 2023
neos-bot
pushed a commit
to neos/neos
that referenced
this issue
May 31, 2023
neos-bot
pushed a commit
to neos/nodetypes-assetlist
that referenced
this issue
May 31, 2023
neos-bot
pushed a commit
to neos/nodetypes-basemixins
that referenced
this issue
May 31, 2023
neos-bot
pushed a commit
to neos/nodetypes-columnlayouts
that referenced
this issue
May 31, 2023
neos-bot
pushed a commit
to neos/nodetypes-contentreferences
that referenced
this issue
May 31, 2023
neos-bot
pushed a commit
to neos/nodetypes-form
that referenced
this issue
May 31, 2023
neos-bot
pushed a commit
to neos/nodetypes-html
that referenced
this issue
May 31, 2023
neos-bot
pushed a commit
to neos/nodetypes-navigation
that referenced
this issue
May 31, 2023
|
Note dispite this being closed, I think we should make a final pass on this in 9.0 with all the new packages. Will tke care before beta on tuesday. |
That should be done, I went through that with my "extraction PR" during the sprint. Nut checking again does no harm. 😎 |
|
It worked as expected |
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 topic?
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: