build: adjust peer dependency to include all minor pre-releases #26421
Conversation
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
Pre-release versions of Angular Material should be compatible with the same pre-release versions of FW (being worked on at the same time). Additionally we want to expand the peer dependency so that the pre-release Material version is also compatible future pre-release of framework. e.g. consider the scenario where Angular framework already released `15.2.0-next.0`, while both CLI and COMP are still on `15.1.0-next.0`. CLI in this case want to depend on the latest versions, but with the recent stricter NPM version this would break as Material wouldn't allow `v15.2.0-next.0` We switch to a more simpler model that requires less changes by the caretaker. For `@next` releases we will be more flexible and allow for all pre-releases of the current major and (N+1)-next/rc Also we no longer require the peer dep to be updated manually. This simplifies the caretaker experience as the peer dependency would no longer need to be updated manually every time the release version changes.
angular-robot
bot
added
the
area: build & ci
devversion
added
target: patch
devversion
added
action: merge
devversion
added a commit
that referenced
this pull request
Jan 12, 2023
Pre-release versions of Angular Material should be compatible with the same pre-release versions of FW (being worked on at the same time). Additionally we want to expand the peer dependency so that the pre-release Material version is also compatible future pre-release of framework. e.g. consider the scenario where Angular framework already released `15.2.0-next.0`, while both CLI and COMP are still on `15.1.0-next.0`. CLI in this case want to depend on the latest versions, but with the recent stricter NPM version this would break as Material wouldn't allow `v15.2.0-next.0` We switch to a more simpler model that requires less changes by the caretaker. For `@next` releases we will be more flexible and allow for all pre-releases of the current major and (N+1)-next/rc Also we no longer require the peer dep to be updated manually. This simplifies the caretaker experience as the peer dependency would no longer need to be updated manually every time the release version changes. (cherry picked from commit 6afe888)
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Pre-release versions of Angular Material should be compatible with the same pre-release versions of FW (being worked on at the same time).
Additionally we want to expand the peer dependency so that the pre-release Material version is also compatible future pre-release of framework. e.g. consider the scenario where Angular framework already released
15.2.0-next.0, while both CLI and COMP are still on15.1.0-next.0.CLI in this case want to depend on the latest
versions, but with the recent stricter NPM version this would break as Material wouldn't allow
v15.2.0-next.0We switch to a more simpler model that requires less changes by the caretaker. For
@nextreleases we will be more flexible and allow for all pre-releases of the current major and (N+1)-next/rcAlso we no longer require the peer dep to be updated manually.
This simplifies the caretaker experience as the peer dependency would no longer need to be updated manually every time the release version changes.