fix(ansible): bump call-release-artifact pin to pick up #127 and #128 - #129
Merged
Merged
Conversation
The pin still referenced 1814f1e, which predates #127 and #128. Left alone the release path would keep calling the old workflow, so the corrected attestation verify command would never reach the release notes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FDecVMyhtUtixsLmT4oLwY
patrick-hermann-sva
temporarily deployed
to
linting
July 29, 2026 13:18 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
patrick-hermann-sva
temporarily deployed
to
linting
July 29, 2026 13:18 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
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.
Mechanical follow-up, same as #126.
call-ansible-collection.yamlpinnedcall-release-artifact.yaml@1814f1e, which predates both #127 (the corrected attestation verify command, now also in the release notes) and #128 (the refreshed dagger defaults).Without this bump both would be merged and look shipped while the release path kept invoking the old workflow — so consumers would keep getting release notes carrying a verify command that fails.
Bumped to
e868d3f, current main.This is the second time a SHA pin has needed a deliberate follow-up commit to take effect. It is the cost of pinning, and worth remembering: merging a change to a pinned reusable workflow does not deploy it.
🤖 Generated with Claude Code
https://claude.ai/code/session_01FDecVMyhtUtixsLmT4oLwY