Repository navigation
ci(release): pin release workflows to the lag-tolerant commit - #36
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
Repins this repository's own release and publish callers from 7857565 to the merged lag-tolerant commit 79c1362 (PR #35), so its next release uses the fixed
create-tag.pyand helper checkouts atjob.workflow_sha.Changes
.github/workflows/release.yml:release-tag.yml@79c1362….github/workflows/publish.yml:release-github.yml@79c1362…[Unreleased]› CI line.Test plan
actionlint: clean.uses:SHAs and the changelog line change; 79c1362 is an ancestor oforigin/main.created, tag and GitHub Release verified.Screenshots
N/A
Risk
Intent
change, depth light: a mechanical repin to an already merged and live-tested commit, with a complete deterministic check. The files are workflows, which the light criteria normally exclude, so this is disclosed here. No behavior change beyond the reviewed #35. This repository's next release tag run will exercise the new pin.How to revert
Revert the merge commit.
Deployment notes
None. No release of this repository is part of this PR.