Repository navigation
chore(release): v5.1.0 - #37
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
Summary
Release v5.1.0 of github-workflows: bump
VERSION5.0.1 → 5.1.0 and move[Unreleased]into## [5.1.0] - 2026-11-11. Delivers the lag-tolerantcreate-tagfix (#35, #36) plus the CI-owned release features merged since v5.0.1.Changes
VERSION: 5.0.1 → 5.1.0.CHANGELOG.md:[Unreleased]entries moved under[5.1.0];[Unreleased]left empty.Test plan
## [5.1.0]section, minor bump justified by the Added/Changed entries.origin/main; tagv5.1.0does not exist on origin.Screenshots
N/A
Risk
Intent
release, depth standard. The independent reviewer subagent was unavailable (usage limit), so the review was done in the principal session; limitation disclosed. CI creates the tagv5.1.0on the merge commit and publishes the GitHub Release; consumers stay pinned by SHA, so nothing changes for them until they repin.How to revert
Do not move or delete the tag. If needed, fix forward with a patch release; a revert of this PR before merge simply drops the bump.
Deployment notes
No migration. After merge, follow the main-push tag workflow run and verify tag
v5.1.0points at the merge commit and the GitHub Release exists. Target branch:main(GitHub flow, squash).🤖 Generated with Claude Code