Pin gdam-actions to v0.0.1 - #3
Merged
Merged
Conversation
gdam-actions restarted its version line: the v0.1.x numbering predated it having a release process and left the two action collections here starting from different numbers for no reason, so those tags are deleted and the line restarts at v0.0.1. @v0.1.2 is a dead ref now, so this is a fix rather than an upgrade -- without it the next run of this workflow cannot resolve the action. v0.0.1 points at the same commit v0.1.2 did, so the content is identical and this still carries the authenticated "latest" lookup that stopped the intermittent 403s. Co-Authored-By: Claude Opus 5 (1M context) <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.
Repins onto gdam-actions v0.0.1.
Why, so soon after the last bump
gdam-actionsrestarted its version line. Thev0.1.xnumbering predated it having any release process and left the two action collections in this workspace starting from different numbers for no reason — so the old tags were deleted and the line restarts atv0.0.1.@v0.1.2is now a dead ref, so this is a fix rather than an upgrade: without it the next run of this workflow cannot resolve the action.Nothing else changed
v0.0.1points at the same commitv0.1.2did. The content is identical — only the name moved. That still includes the fix from the last bump:installauthenticates the API call that resolveslatest, which was returning 403 several times an hour from shared CI runner addresses.Ref-only diff: the
uses:line and nothing else.