ci: adopt Changesets for versioning#9
Merged
Merged
Conversation
…h.yml) Mirrors the kura setup. Contributors run 'bun run changeset'; the changesets.yml workflow opens a 'Version Packages' PR (changeset version → bumps + CHANGELOGs); publishing stays with the tag-triggered publish.yml (idempotent OIDC trusted publishing). Verified against June's specifics (catalogs + workspace:^ + ranges): - catalog: deps (react family) are left untouched (react isn't a workspace package). - workspace:^ (juno → @junejs/server) is left untouched (bun pm pack rewrites it at publish). - internal >=X <0.1.0 ranges are preserved when they already cover the new version; a range is only rewritten (e.g. >=0.0.46 <0.1.0 → >=0.0.47) when one changeset co-bumps a package AND its internal dep, which is the coordinated case where the newer floor is intended.
The default changelog lists changeset summaries; changelog-github additionally resolves each entry
to its PR and author ("[#42](link) Thanks [@user]! - summary") — better for public packages. It
needs GITHUB_TOKEN at `changeset version` time, which the changesets/action provides; contributors
only run `changeset add` locally (no token needed).
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
1 participant
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.
Mirrors the kura Changesets setup (kurajs/kura#12), with June-specific verification of the catalog + workspace:^ + range mix.
Flow
bun run changesetto describe a change + bump type.changesets.yml(push to main) opens/updates a "Version Packages" PR (changeset version→ bumps versions, cascades dependents only when needed, writes CHANGELOGs).publish.yml(idempotent OIDC trusted publishing viabun pm pack+npm publish). The proven publish flow is untouched.Verified against June's specifics (probed by co-bumping @junejs/core + @junejs/server)
catalog:deps (react family) left untouched — react isn't a workspace package.workspace:^(juno → @junejs/server) left untouched —bun pm packrewrites it at publish.>=X <0.1.0ranges preserved when they already cover the new version (e.g. cli→core stayed>=0.0.46 <0.1.0when only core bumped).>=0.0.46 <0.1.0→>=0.0.47), dropping the<0.1.0upper bound. That's the coordinated case where requiring the newer floor is intended; independent bumps preserve the full range.Config:
access: public,baseBranch: main. No package code changed, so no changeset accompanies this PR.