chore(ci): do not enforce changeset entry for certain milestones #10858
Conversation
This file contains 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
Josh-Walker-GM
added
the
release:chore
Tobbe
approved these changes
Jun 19, 2024
Josh-Walker-GM
added a commit
that referenced
this pull request
Jun 25, 2024
) Right now the check will enforce a changeset entry for any PR. We have noticed this can be a bit excessive for the current RSC/SSR work. These features are not scheduled for stable release in the near future and so requiring a changeset on every related PR can produce changesets which are of little value - descriptions of fixes for features that have never been released in stables.
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.
Right now the check will enforce a changeset entry for any PR. We have noticed this can be a bit excessive for the current RSC/SSR work. These features are not scheduled for stable release in the near future and so requiring a changeset on every related PR can produce changesets which are of little value - descriptions of fixes for features that have never been released in stables.