release: 0.3.0#57
Merged
Merged
Conversation
Fold the accumulated changelog fragments into a [0.3.0] section, backfill the post-0.2.0 history (TanStack Query, prod-build smoke, db typecheck, the #30–#40 stabilization batch), bump the version, and add the migration guide. - package.json: version 0.2.0 -> 0.3.0 - CHANGELOG.md: new ## [0.3.0] section (22 tagged entries) assembled via `pnpm changelog:release`; fragments consumed - docs/migrations/v0.3.md: migration guide covering every [propagate] entry [skip-changelog] release PR consumes fragments; adds none.
A release PR assembles and consumes fragments rather than adding one, so it would otherwise fail the changelog-fragment guard. Exempt `release/*` head branches (alongside the existing `skip-changelog` label). Documented in changelog.d/README.md.
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
2 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.
Cuts the 0.3.0 release (minor — additive features, no breaking instance-code changes; Node ≥ 22 is now required).
What's in it
package.json:0.2.0→0.3.0.CHANGELOG.md: a new## [0.3.0]section assembled from the accumulatedchangelog.d/fragments viapnpm changelog:release(fragments consumed). 22 tagged entries.docs/migrations/v0.3.md: migration guide covering every[propagate]entry, in dependency order.Scope (comprehensive)
This release captures everything since 0.2.0, not just this session's batch. The fragments system only started mid-stream, so I backfilled changelog entries for the earlier post-0.2.0 merges (reconstructed from commit history — worth a skim):
db/type-check +~/dbalias (fix: type-check db/ and make the ~/db import alias resolve #40), and the fix: restore red CI — workflow gating, lockfile, @tanstack build, and scaffold stdin #30–ci: harden workflows — permissions, concurrency, SHA-pinned actions #39 stabilization batch (stylesheet?url, lazy env/db, Hono OPTIONS/HEAD + error handling, hydration/CRLF fixes, scaffold/workflow hardening).Note on CI
This PR also adds a one-line CI change: the
changelog-fragmentjob now exemptsrelease/*branches (a release consumes fragments, it doesn't add one). Theskip-changeloglabel is defined inlabels.mjsbut isn't created on the repo, so the branch-name exemption is the reliable path for release PRs. Documented inchangelog.d/README.md.Verification
pnpm preflightgreen (44 tests);pnpm changelog:checkclean (fragments consumed); the release-check tag validator passes ("All 22 CHANGELOG entries for [0.3.0] have propagation tags"); version +## [0.3.0]+docs/migrations/v0.3.mdall present forrelease-check.yml.🤖 Generated with Claude Code
Generated by Claude Code