chore: release v1.1.0 - #205
Merged
Merged
Conversation
- bump package version 1.0.0 -> 1.1.0 (the field had drifted; tags were at v1.0.5) - repoint README usage examples to v1.1.0 - align the dev-setup node note with the engines floor Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UTdciRVE8crbaoxq4JyXt4
aeaa1998
marked this pull request as ready for review
August 28, 2026 19:34
weiyin
approved these changes
Aug 28, 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
3 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.
Release bump for the Node 24 work now on
main(#202, #203, #204).Changes
package.json/package-lock.json1.0.0→1.1.0README.md@v1.0.5→@v1.1.0README.mdenginesfloor agreed in #202 — now states 18.18+, with Node 24 recommended for anyone committing a rebuiltdist/No source or
dist/changes.Note on the version field
package.jsonwas on1.0.0while released tags had reachedv1.0.5— the field has never tracked releases. Setting it to1.1.0here fixes that drift, so it now matches the tag.What's in this release
node16→node24; CI on Node 24.x;enginesset to the toolchain floor; TS target ES2024dist/1.36MB → 655KBactions/checkoutv4.3.0 → v7.0.1,setup-nodev4.3.0 → v7.0.0,upload-artifactv4.6.2 → v7.0.1Why minor, not patch
The
node16→node24runtime change is consumer-visible: self-hosted runners need runnerv2.327.1or later. GitHub-hosted runners are unaffected, and the repo has no floatingv1tag — consumers pin exact versions — so nobody is upgraded without editing their workflow.v1.0.5stays available for anyone on an older runner.Beyond the CVE list, #203 fixes a real bug for proxied environments: axios older than 1.16.1 issues non-CONNECT requests for HTTPS, so the action currently fails outright behind a corporate egress proxy.
After merge
Tag
v1.1.0onmain.🤖 Generated with Claude Code
https://claude.ai/code/session_01UTdciRVE8crbaoxq4JyXt4
Generated by Claude Code