Repository navigation
versions: with owner/repo <name>, an entry moved with another repository's - #113
Merged
Merged
Conversation
…ory's What one repository pins because another does was follows <repo>, a note nobody was told about: spin-ami rebuilds the Grafana and VictoriaMetrics spin lays, at spin's tags, and builds the Alloy whose configuration spin tests, and nothing said when spin moved one. with owner/repo <name> [pin] reads that repository's versions.yaml through GitHub's API, as its default branch has it now - GITHUB_TOKEN or GH_TOKEN for a private one - so check says the entry is behind the day the other moves, and a bump takes what the other has, spelled as this entry spells its own. The gate reads no network, so it holds only the entries with one of the same file; another repository's is check's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
aledbf
force-pushed
the
versions-with-repo
branch
from
November 18, 2026 19:25
2e30fd0 to
4b76b35
Compare
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.
What one repository pins because another does was follows , a note
nobody was told about: spin-ami rebuilds the Grafana and VictoriaMetrics
spin lays, at spin's tags, and builds the Alloy whose configuration spin
tests, and nothing said when spin moved one. with owner/repo [pin]
reads that repository's versions.yaml through GitHub's API, as its default
branch has it now - GITHUB_TOKEN or GH_TOKEN for a private one - so check
says the entry is behind the day the other moves, and a bump takes what the
other has, spelled as this entry spells its own.
The gate reads no network, so it holds only the entries with one of the same
file; another repository's is check's.
Tried against spin: spin-ami's alloy, grafana and victoriametrics as
with spin-stack/spin <name>agree with spin's file with a token, and without one check says it answered 404 and that a private repository needs GITHUB_TOKEN or GH_TOKEN.🤖 Generated with Claude Code