Skip to content

chore: 0.9.0 - #29

Merged
likeBloodMoon merged 1 commit into
masterfrom
claude/release-roadmap-0-8-0-v79592
Sep 25, 2026
Merged

likeBloodMoon merged 1 commit into
masterfrom
claude/release-roadmap-0-8-0-v79592

Conversation

@likeBloodMoon

Copy link
Copy Markdown
Owner

This is the release commit for 0.9.0. It also carries 0.8.0, which was never published.

Why 0.8.0 is skipped

The v0.8.0 tag was pushed to the merge of #27, where package.json still said 0.7.0. The release workflow stopped at its version check, so nothing reached npm. The changes in 0.8.0 now ship in 0.9.0.

What changes

  • package.json is now 0.9.0.
  • CHANGELOG:
    • The 0.9.0 section is dated 2026-09-24. It says this release includes 0.8.0 and that the citation check is still open.
    • The 0.8.0 heading becomes "not published", with the reason.
  • README: a new 0.9.0 paragraph.
  • ROADMAP: both Done means entries now record that the release went ahead with the citation check open. The full check against the primary text is now a 1.0 blocker.
  • The action pin is v0.9.0 in docs/integrations.md and .github/workflows/accessibility.yml.
  • examples/ are regenerated; only the version stamp changed.

Citations

Eight countries still carry the unverified marker: BE, CZ, DK, FI, IE, PL, PT and SE. Their citations were cross-checked against search excerpts from the official sites, and all of them agree. The check against the full laws hasn't been done yet.

After merge

  1. Delete the failed tag: git push --delete origin v0.8.0.
  2. Tag the merge commit as v0.9.0 and push the tag. That runs the release workflow, which publishes to npm.

Testing

  • pnpm lint and pnpm typecheck: clean.
  • pnpm test: 1403 passed. The only failure is the Playwright suite, which needs a Chromium this environment doesn't have; it passes in CI.
  • pnpm smoke: green.
  • pnpm examples: the only change is the version stamp.

🤖 Generated with Claude Code

https://claude.ai/code/session_013BXnvSeRtgZoTXe4j753gM


Generated by Claude Code

Version, the changelog headings, the front page, the ROADMAP's Done-means and
the pinned action tag in docs/integrations.md and
.github/workflows/accessibility.yml. The examples move with it and nothing
else in them does: the tool version is stamped into four of them.

0.8.0 is not published. Its tag was on the merge of #27, where package.json
still said 0.7.0, and the release workflow stopped at its version check before
anything reached npm. Rather than publish it from an older commit, its changes
ship in 0.9.0, and the changelog says so under both headings.

The citation check ships open, as the changelog and ROADMAP now say: the eight
new countries keep the unverified marker, and the full check against the
primary text moves to 1.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013BXnvSeRtgZoTXe4j753gM

Copy link
Copy Markdown
Owner Author

github-advanced-security is red, but the failure is not caused by this PR. GitHub's Copilot code-scanning agent stopped before looking at the diff: CAPIError: 400 The requested model is not supported. This is the same error as on #27 and #28, and a fix has to come from GitHub or from the repository's code-scanning settings. The repository's code has nothing to fix. I can't re-run the check from here.


Generated by Claude Code

@likeBloodMoon
likeBloodMoon marked this pull request as ready for review September 25, 2026 07:54
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@likeBloodMoon
likeBloodMoon merged commit 8fb1236 into master Sep 25, 2026
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants