chore(release): version packages - #450
Merged
Merged
Conversation
Consume all pending changesets and bump each package's beta version per Changesets pre mode (tag: beta). No major bumps are pending, so every package advances within its 0.1.0-beta.N line (or lands its first 0.1.0-beta.0 for cf-shims, deno-host, and mf2). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MJF4pvWtSB6tDxyG1eQj4b
davidwkeith
commented
Jul 24, 2026
davidwkeith
left a comment
Owner
Author
There was a problem hiding this comment.
Reviewed for CONTRIBUTING.md conformance. This is a mechanical changeset version output (185 pending changesets consumed), and it checks out:
- PR title/scope:
chore(release): version packagesmatches the precedent set by the last release PR (#377), which used the identical title — consistent with the Conventional Commits convention for a repo-wide chore. - PR body: opened from the template with
Summary/Packages affected/Checklistheadings intact; unchecked items have one-line reasons rather than being deleted. - Diff scope: touches only
package.jsonversions,CHANGELOG.mdadditions, and.changeset/pre.json— no source changes, so "not applicable" on the tests/spec checklist items is accurate. - Version bumps: all 31 packages bump by exactly one prerelease integer (
beta.N→beta.N+1), no unexpected major bumps;@dwk/cf-shims,@dwk/deno-host,@dwk/mf2correctly land their first0.1.0-beta.0, matching the PR description. - Pre-mode changeset behavior: individual
.changeset/*.mdfiles are intentionally not deleted (Changesets pre mode keeps them untilpre exit), matching what #377 did — not a bug. - CI: release-gate, integration, CodeQL, and catalog checks are green;
build-testwas still in progress as of this review.
No changes requested — nothing here needs fixing. (Note: couldn't submit as an "Approve" since this PR is authored by the same account this review is posted from — GitHub disallows self-approval.)
Generated by Claude Code
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.
Summary
Cuts the next beta release: consumes all 185 pending changesets and applies
their version bumps via
pnpm changeset version(Changesets pre mode, tagbeta). No pending changeset was amajorbump, so every package advanceswithin its existing
0.1.0-beta.Nline —@dwk/cf-shims,@dwk/deno-host,and
@dwk/mf2land their first0.1.0-beta.0. No package reaches a stable1.0.0; that stays blocked behind conformance (conformance/status.jsonstill shows most hosted suites as
pending).This is the version-bump step of the routine beta-release path in
RELEASING.md. After this merges tomain,the next steps (outside this PR) are a
dry_run: trueand thendry_run: falsedispatch of the Release GitHub Actions workflow toactually publish to npm.
Packages affected
All 31 publishable workspace packages (see the diff for the full list);
@dwk/serverand@dwk/conformance-targetbump too but are never publishedto npm.
Checklist
spec/packages/and updated them ifbehaviour changed — not applicable, no behaviour changed, version-only
src/*.test.ts) — not applicable,version-only change
pnpm lint && pnpm format:check && pnpm typecheck && pnpm build && pnpm testpnpm changeset) if this touches a publishablepackage — not applicable, this PR consumes the pending changesets
catalog.json/conformance/status.jsonif this adds a newmountable worker or changes conformance status — not applicable, no
catalog/conformance changes;
pnpm release:gateandpnpm catalog:checkboth passGenerated by Claude Code