Release 0.9.1, add release:check, and the plan for 1.0 - #31
Merged
Merged
Conversation
Replaces the one-line 1.0 outline with a full plan: stack detection that covers Next.js properly (build manifests as the page list, standalone and export output, basePath and i18n), the missing frameworks, monorepos and package managers; the contracts frozen with published JSON Schemas and surface locks; an acceptance matrix and a hostile-input suite; speed work measured against 0.9.0 with a new --against mode; release checks that would have caught 0.8.0; and a date-aware Swedish authority. Each item names its gate and exit condition, and the release itself runs as an rc loop that exits on a clean candidate plus seven clean nightly soaks. Four decisions are listed at the end for review before work starts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013BXnvSeRtgZoTXe4j753gM
The corrected Danish, Czech and Portuguese statement templates, and `pnpm release:check`: the tag matches package.json, the changelog has a dated heading and no Unreleased section, the Action pins and examples are at this version. CI runs it on PRs that change the version, and the release workflow runs it against the tag before publishing. ROADMAP: the 1.0 plan as a product, with the release steps 0.9.1, 0.10.0, 0.11.0 and the 1.0.0 release candidates. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013BXnvSeRtgZoTXe4j753gM
likeBloodMoon
changed the title
likeBloodMoon
marked this pull request as ready for review
September 26, 2026 17:40
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.
0.9.1
pnpm release:check(scripts/release-check.ts) refuses a commit that is not ready to tag. It checks that:package.json;CHANGELOG.mdhas a dated## <version> — YYYY-MM-DDheading and noUnreleasedsection;likeBloodMoon/eaa-kit@vXpin in README, docs and workflows is at this version;examples/was generated by this version.release.ymlnow runspnpm release:check "$GITHUB_REF_NAME"in place of its inline tag check.pnpm exampleshas been re-run.The plan for 1.0 (ROADMAP.md)
The 1.0 section describes the finished product, then the steps to get there:
detectanddoctor.audit()/detect()API.Tests
pnpm lint,pnpm typecheckandpnpm smokepass.pnpm release:checkandpnpm release:check v0.9.1pass;pnpm release:check v0.9.2fails, as it should.pnpm testhas six new tests for release:check. A mutation check confirmed the tag test fails when the tag check is removed.test:packagedfail on master too (Chromium mismatch). CI is unaffected.After merge (maintainer)
git tag v0.9.1 && git push origin v0.9.1git push --delete origin v0.8.0🤖 Generated with Claude Code
https://claude.ai/code/session_013BXnvSeRtgZoTXe4j753gM