Repository navigation
Conversation
Contributor
Author
|
Closing as stale/hazardous per automate-talos-upgrade-pipeline task 8c. PR #14 names OCI images deleted by the contingency prune (5.4a) and predates the version-drift gate. The current pipeline regenerates a correct PR on demand; nothing is lost. |
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.
Talos image update
oracle4a0d65c669d46663f377e7161e50cfd570c401f26fd9e7bda34a0216b6f1922b(tailscale only)Canonical OCI consumer file remains
omni/talos-image.yamland points at the Oracle-platform image when built.Check Pluto output for deprecated API versions before merging.