Repository navigation
chore: adopt changesets for versioning and release notes - #219
Merged
Merged
Conversation
This was referenced Oct 6, 2026
Owner
Author
This was referenced Oct 6, 2026
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
This was referenced Oct 6, 2026
pbroom
force-pushed
the
chore/packaging-and-licensing
branch
from
October 8, 2026 02:44
162a719 to
3889ffa
Compare
pbroom
force-pushed
the
chore/adopt-changesets
branch
from
October 8, 2026 02:44
76de170 to
00b0329
Compare
This was referenced Oct 8, 2026
This was referenced Oct 8, 2026
Owner
Author
pbroom
changed the base branch from
chore/packaging-and-licensing
to
graphite-base/219
October 10, 2026 19:25
- Add @changesets/cli (v3) with `changeset` and `version-packages` scripts. - Configure changesets so only the published `color-kit` facade is versioned (privatePackages: version/tag false); plain 0.x versions, with the `next` dist-tag still coming from publishConfig. - Drop the two stale @color-kit/react changesets: they target a private, never-published package and predate the 0.1.0 release prep, so changesets would silently skip them. - check:preprod now rejects changesets that target non-publishable packages or use a major bump while the package is pre-1.0. - Add a Version Packages workflow (changesets/action, version PR only, no npm publishing or token); publishing stays manual via pnpm publish:next. - Document the flow in CONTRIBUTING.md and README, and add a changeset for the facade peer/color-input/licensing changes. Co-Authored-By: Claude Opus 5.5 <[email protected]>
@changesets/cli 3 requires Node ^22.11, but the workspace supports Node >=20. 2.31.1 and its dependency tree run on Node 20. Co-Authored-By: Claude Opus 5.5 <[email protected]>
…arse Lines with a trailing YAML comment or other syntax were silently skipped, so a release targeting a private package could pass check:preprod. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
changesets/action v2 (ae32849, v2.1.2) calls validateChangesetsCliVersion
from every mode and throws when the root package declares or resolves
@changesets/cli 2.x ("use Changesets action v1 instead"). We pin the CLI
to ^2.31.1 to keep Node 20 support, so the Version Packages workflow
would fail on main. Pin v1.9.0 (a45c4d5, node24 runtime), which has no
CLI-version gate and runs `changeset version` (or the version script)
for CLI >= 2, and switch to its input names: version, commit, title.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
pbroom
force-pushed
the
chore/adopt-changesets
branch
from
October 10, 2026 19:27
00b0329 to
fbf0e6e
Compare
This branch was successfully deployed
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.

changesetandversion-packagesscripts.color-kitfacade isversioned (privatePackages: version/tag false); plain 0.x versions, with
the
nextdist-tag still coming from publishConfig.never-published package and predate the 0.1.0 release prep, so changesets
would silently skip them.
packages or use a major bump while the package is pre-1.0.
npm publishing or token); publishing stays manual via pnpm publish:next.
the facade peer/color-input/licensing changes.
Part of a stacked set of PRs (#204 → #221) from the color-kit assessment. Validated per branch with
pnpm buildandpnpm test; lint, format, typecheck, size, artifact, preprod and agents checks pass at the top of the stack.🤖 Generated with Claude Code