chore(release): prepare v1.1.5 - #448
Merged
Merged
Conversation
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, and no runtime behavior or public API changed. Also records the [Unreleased] changelog entry for #446, which merged without one. That work — Vitest 5, @types/node 26, esbuild, eslint, typescript-eslint — is development tooling and is not published, though it does clear the two development-only advisories that v1.1.4 explicitly did not claim. Refs #447 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
On-demand reviews are free for the next 29 days. After that, they cost $0.25 per reviewed file. Or wait 21 minutes for your next included review. View limit detailsLimit details: You’ve used the included review currently available. Your 108 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (7)
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
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. Prepares the compatible v1.1.5 patch release.
What reaches installers
Only one thing:
@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.
What does not reach installers
Everything else landed in #446 is development tooling: 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 replaced a fragileAwaited<ReturnType<typeof stat>>idiom with the concreteStatstype; those are type-only and erased at compile time.That work does clear the two development-only advisories v1.1.4 explicitly did not claim, so both the production-only and full npm audits now report zero — but that is this repository's toolchain, not the published artifact.
Changelog gap closed
#446 merged without an
[Unreleased]entry. This PR records it, so the 1.1.5 notes describe both the shipped dependency refresh (#447) and the toolchain work (#446).Version
package.jsonandpackage-lock.json(bothversionandpackages[""].version) move to1.1.5, no local tag. Pinned version documentation (README.md,docs/presets-and-clients.md,docs/mcp-compatibility.md,docs/whats-new-in-0.5.md) and the release-contract tests are aligned. Changelog dated 2026-09-11, linking the release issue.Selected from the version actually published to npm (
1.1.4); compatible changes only.Verification
npm run typecheck,npm run lint,npm run build,npm run check:test-fixture,npm run check:pack("Package contract verified (58 files)"), and thenode dist/cli/main.js schemasmoke test are all cleannpm audit: zero, production-only and full🤖 Generated with Claude Code