chore: enable yarn deferred versioning - #3436
Draft
zbynekstara wants to merge 1 commit into
Draft
Conversation
| # = Everything below is IGNORED (never triggers a bump) | ||
|
|
||
| # Tests, mocks, benchmarks, demos, stories (not shipped) | ||
| - "**/*.test.{js,ts,mjs}" |
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
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.
Description
Adopt Yarn's deferred versioning so the intended release type (patch / minor / major) for each publishable
@joint/*package is declared per pull request instead of being hand-applied at release time.Contributors run
yarn version-checkand commit a small.yarn/versions/*.ymlfile describing their bump; CI blocks PRs that change a publishable package without one. At release a maintainer runsyarn version-applyto apply all accumulated bumps at once (Yarn rewrites cross-packageworkspace:ranges automatically).Motivation and Context
Releases are currently fully manual: a maintainer hand-edits each
package.jsonversionand theCHANGELOG, then tags and publishes. Nothing records what kind of release a normal PR implies, so the bump decision is deferred to one person at the end and is easy to get wrong. Deferred versioning captures that intent at PR time, i.e. by the author with the most context, and makes the release step mechanical.