chore(release): bump internal self-references to v1.1.0 ahead of tagging - #48
Merged
Conversation
Co-authored-by: Claude Opus 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
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.
Step 2 of the release process added in #44 — the one that is easy to forget and silently ships nothing.
These workflows call this repo's own composite action by its full external form (
lentago/shared-workflows/.github/actions/render-claude-summary@<ref>) rather than a relative./path, because inside a reusable workflow./resolves against the caller's repo, not this one. That makes the ref a version pin which has to move deliberately.If it stayed at
@v1.0.0whilev1.1.0was tagged, the workflows inside v1.1.0 would keep running v1.0.0's action — a fix to the composite action would ship to nobody while the release notes claimed otherwise. Bumping first, merging, then tagging this commit means the refs resolve correctly the moment the tag exists.What v1.1.0 adds over v1.0.0: the
site-deploy.ymlreusable (#38/#47) — the three site repos' near-identical deploy pipelines extracted into one workflow, with an image scan and build-provenance attestation folded in; this repo's own Scorecard workflow (#43); and the grouped Dependabot config.Verified per RELEASING.md step 2:
grep -rn 'shared-workflows/.github/actions/.*@v' .github/ | grep -v v1.1.0returns nothing.