feat: adopt changesets for versioning and releases - #118
Merged
Conversation
Replace the tag-triggered publish workflow with a changesets-driven flow and seed the historical changelog so future releases build on it. - package.json becomes the version source of truth (0.8.0, private); the publishable artifact remains build/npm produced by dnt. - .changeset config uses @changesets/changelog-github against bombshell-dev/tty. - release.yml runs changesets/action on main: it opens a "Version Packages" PR from pending changesets, and on merge runs the publish command (npm run release). - tasks/release.ts wraps the Deno/dnt flow: build:npm, publish build/npm, then tag v<version> and push. It no-ops when the version is already on npm, because changesets/action runs the publish command on every changeset-less push to main. Tags keep the existing v<version> format for continuity with v0.0.0..v0.8.0. - CHANGELOG.md seeds all 14 releases in changelog-github format, with PRs attributed by the tag range their merge commit falls in and authors credited. - deno.json fmt excludes CHANGELOG.md/.changeset so deno fmt does not rewrap changesets output.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
commit: |
gameroman
reviewed
Sep 1, 2026
Bump @changesets/cli ^2.29.7 -> ^3.0.1 and @changesets/changelog-github ^0.5.1 -> ^1.0.0, tracking the transitive @changesets/config@4.0.0 in the config schema URL. v3 stops versioning private packages by default. @bomb.sh/tty is `private: true` (root is a build source; publish happens from build/npm via tasks/release.ts), so opt back in with privatePackages.version. Leave privatePackages.tag off because release.ts owns git tagging.
Cover everything landed since v0.8.0 that affects the published package; resolves to a 0.9.0 minor bump. - #116 border sides reserve layout space (minor, breaking within 0.x) - #103 hardware cursor via text() caret (minor) - #89 compile out Clay debug-tools, ~35% smaller wasm (patch) - #49 correct width for non-printable/surrogate codepoints, Unicode 17 (patch) Dependabot/CI bumps, the 2048 example, and docs-only commits get no changeset.
Rework the backfilled history to match the changeset message style used for new entries: - Third-person present verbs throughout (Adds/Fixes/Renames), so future changeset-generated entries read consistently against the history. - Reframe entries toward user-visible impact, dropping wire-format and build-mechanism detail that consumers can't act on. - Drop non-user-facing entries (CI, tooling, tests, benchmarks, examples, internal docs); keep LICENSE since it ships in the package. - Hoist the breaking Op->directive/name->id rename to the top of its Patch section (bump stays patch; it already shipped).
dreyfus92
reviewed
Sep 1, 2026
dreyfus92
left a comment
dreyfus92
left a comment
Member
There was a problem hiding this comment.
awesome job @natemoo-re, left a few comments 🤘🏻
natemoo-re
force-pushed
the
nm/feat/changesets
branch
from
September 1, 2026 04:01
540792a to
5f96919
Compare
Member
Author
|
bonus fix: the changeset action inputs changed in v2, updated ours to match in f96244f |
dreyfus92
approved these changes
Sep 1, 2026
dreyfus92
left a comment
dreyfus92
left a comment
Member
There was a problem hiding this comment.
looks good to me! thank you @natemoo-re 💜
Trim to the level of detail each bump warrants: patches to a single sentence, the caret minor to one paragraph. The breaking border change keeps its two paragraphs plus migration diff.
jbolda
approved these changes
Sep 1, 2026
jbolda
left a comment
jbolda
left a comment
Member
There was a problem hiding this comment.
We might also want to consider a couple new rulesets.
- As we have a script which runs as part of our publish process, we may want to require extra reviews or from specific code folks if one edits the build script in a PR.
- We could also consider more reviews on the release PR as a require. For example, 1 review to merge, 2 to publish? This feels up more for discussion than the previous bullet point.
Approval as I don't see any of these as hard blocks.
Rely on structured --json output instead of plain-text stdout when checking whether the version is already on npm.
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
4 participants
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.
What does this PR do?
Replace the tag-triggered publish workflow with a changesets-driven flow and seed the historical changelog so future releases build on it.
package.jsonbecomes theversionsource of truth (v0.8.0) and the published artifact produced bydntderives from that.Type of change
Checklist
pnpm test)pnpm format)AI-generated code disclosure