Repository navigation
sync: the chain report says which release images.json has an image of - #59
Merged
Merged
Conversation
The installation pages name the newest release with an image, so a release without one is documented and installed by nobody; the chain report showed every link but that one. Co-Authored-By: Claude Opus 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.
spin#657's chain table now has an
images.jsonrow: the newest spin release with an AMI against spin's newest release. While no AMI was being built (10-19 to 10-25), the issue did not show it.Against the real API now:
| images.json | has an image of spin's newest release, v20261025.01 |. Tested with a fixture that has an unbuilt release, and with v20261019.10 ordered after v20261019.9.🤖 Generated with Claude Code