chore(release): promote v1.1.5 to main - #449
Merged
Merged
Conversation
Brings the v1.1.3 promotion merge (ea1cbf8) into development's ancestry so the two persistent branches do not drift by identity. Content-neutral: the merge introduces no file changes, it only restores containment so promotion PRs stop reporting BEHIND. Refs #441 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
chore: sync main release history into development
Supersedes #445, #438, #437, #436, #435, none of which could go green alone. Vitest 3.2.7 -> 5.0.0 with @vitest/coverage-v8 and vite as an explicit devDependency (Vitest 5 declares vite a non-optional peer). @types/node 22 -> 26, @hono/node-server 2.0.10 -> 2.1.1, esbuild 0.28.1 -> 0.28.2, eslint 10.8.0 -> 10.10.0, typescript-eslint 8.65.0 -> 8.70.0. Both the production-only and full npm audits now report zero. @types/node 26 added a throwIfNoEntry overload to stat(), so Awaited<ReturnType<typeof stat>> resolves to Stats | BigIntStats | undefined and keyof of that union is never. Replaced the idiom with the concrete Stats type in the three files using it. Vitest 4 removed test.poolOptions and promoted its contents to top-level options. Vitest 5 applies AST-aware remapping unconditionally, so function and branch figures are not comparable across the migration; thresholds recalibrated to measured actuals with line thresholds unchanged. zod 4.2.0 -> 4.6.2 deliberately held: the evidence-pinned bundled fixture embeds zod, so bumping it invalidates the sha256 that the named-host evidence ledger pins. Lock-only hold; the declared ^4.2.0 range is unchanged. Refs #435, #436, #437, #438, #445 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Finalize the compatible v1.1.5 patch release. The only change that reaches installers is the @hono/node-server runtime dependency, refreshed from 2.0.10 to 2.1.1. Neither version carries a security advisory, so this is a dependency refresh rather than a security release; no runtime behavior or public API changed. Also records the [Unreleased] changelog entry for #446, which merged without one. That work is development tooling and is not published, though it does clear the two development-only advisories v1.1.4 explicitly did not claim. Refs #447 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
This was referenced Sep 11, 2026
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
1 participant
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.
Refs #447. Release promotion of
developmenttomainfor v1.1.5.Merge with a merge commit, never squash. Squashing bakes the content into a new SHA that
developmentnever receives, drifting the two persistent branches by identity and producing phantom conflicts on the next promotion.Contents
What reaches installers
Only
@hono/node-server2.0.10 → 2.1.1, a runtime dependency. Neither version carries a security advisory, so this is a dependency refresh, not a security release. No runtime behavior and no public API changed.Everything else is development tooling that is not published: Vitest 3.2.7 → 5.0.0 with
@vitest/coverage-v8and an explicitvitepeer,@types/node22 → 26,esbuild0.28.1 → 0.28.2,eslint10.8.0 → 10.10.0,typescript-eslint8.65.0 → 8.70.0. The accompanying source edits are type-only and erased at compile time.That toolchain work clears the two development-only advisories v1.1.4 explicitly did not claim, so both the production-only and full npm audits now report zero — for this repository, not the published artifact.
Verification at this head
npm run typecheck,npm run lint,npm run build,npm run check:test-fixture,npm run check:pack("Package contract verified (58 files)"), and the CLI smoke test are cleannpm audit: zero, production-only and fullAfter merge
Create the GitHub Release for
v1.1.5at the exact resultingmaincommit, which triggers.github/workflows/publish.ymland npm trusted publishing. NoNPM_TOKEN, no workstationnpm publish. This release does not authorize removal of any legacy behavior.🤖 Generated with Claude Code