Repository navigation
chore: version 2.1.1 - #158
Merged
Merged
Conversation
Everything on main since v2.1.0 (a1cf211, May) is dependency and CI work: src/ and action.yml are untouched, so @v2 keeps working. The bundle in dist/ has been rebuilt over that stretch for undici 6.29.1 (GHSA advisories), handlebars 4.7.10 and brace-expansion 2.1.7/5.0.12. v2 still points at a1cf211, so none of that reaches consumers until the major tag moves. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AfXo7y92vCvoKLLaVgj5XM
|
| User | Commit | Date |
|---|---|---|
| noreply@anthropic.com | chore: version 2.1.1 | October 27, 2026 |
| gimenez.maxi@gmail.com | fix(deps): bump brace-... | October 23, 2026 |
vCaisim
approved these changes
Oct 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
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.
Bumps
package.jsonandpackage-lock.jsonfrom2.1.0to2.1.1, so a release can be cut frommain.Why a patch
v2.1.0points at a1cf211 (14 May 2026). The 27 commits onmainsince then are all dependency and CI work —src/andaction.ymlare untouched, so@v2keeps working for existing consumers.Why it is worth releasing now
v2still points at a1cf211, so everything rebuilt intodist/since May is sitting unreleased. That includes the security bumps:undici→ 6.29.1, for GHSA advisories (chore(deps): bump undici from 6.28.0 to 6.29.0 #145, f1926a8)handlebars→ 4.7.10 (chore(deps-dev): bump handlebars from 4.7.9 to 4.7.10 #150, fix(deps): bump handlebars to 4.7.10 in the lockfile #151)brace-expansion→ 2.1.7 and 5.0.12 (chore(deps): bump brace-expansion #132, fix(deps): bump brace-expansion to 5.0.12 and 2.1.7 in the lockfile #152)Those ship in the bundled
dist/, so consumers on@v2only pick them up once the major tag moves.After merge
script/releasecutsv2.1.1and movesv2.Generated by Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.