Repository navigation
Conversation
Contributor
Author
|
Superseded by #9 (Talos v1.13.5), which is the newest installer actually built. Closing to leave a single upgrade target. Reopen if you want to step through intermediate Talos versions deliberately. |
syscod3
added a commit
that referenced
this pull request
Aug 3, 2026
… workflow The pluto job read kubernetes_version from omni/talos-image.yaml, which is the build ledger — it records what was last built, not what clusters run. With the ledger at v1.37.0-beta.0 and clusters on v1.36.3, the deprecation gate was checking the wrong target entirely. It now reads the desired pin from omni/versions.yaml and fails if that pin is missing. talos-image-update.yml was a second, competing PR-opening path: a repository_dispatch receiver that sed-bumps talos_version in the ledger and opens its own PR on a different branch from the one talos-images/build.yml opens. No sender exists in any repo (grepped all of ~/syscode/git), so it is orphaned — but if it ever fired it would bump talos_version without schematic_id or oci_image_ocid, producing a ledger pointing at a version whose image was never built. That is root cause #4 of the 2026-08-03 incident. Refs: openspec/changes/automate-talos-upgrade-pipeline
syscod3
added a commit
that referenced
this pull request
Aug 8, 2026
… workflow The pluto job read kubernetes_version from omni/talos-image.yaml, which is the build ledger — it records what was last built, not what clusters run. With the ledger at v1.37.0-beta.0 and clusters on v1.36.3, the deprecation gate was checking the wrong target entirely. It now reads the desired pin from omni/versions.yaml and fails if that pin is missing. talos-image-update.yml was a second, competing PR-opening path: a repository_dispatch receiver that sed-bumps talos_version in the ledger and opens its own PR on a different branch from the one talos-images/build.yml opens. No sender exists in any repo (grepped all of ~/syscode/git), so it is orphaned — but if it ever fired it would bump talos_version without schematic_id or oci_image_ocid, producing a ledger pointing at a version whose image was never built. That is root cause #4 of the 2026-08-03 incident. Refs: openspec/changes/automate-talos-upgrade-pipeline
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 upgrade
4a0d65c669d46663f377e7161e50cfd570c401f26fd9e7bda34a0216b6f1922b(tailscale only)ocid1.image.oc1.uk-london-1.aaaaaaaayv53eqanqk7dovyqur5hkjhwosnel4itvah26bofeesgzwpapvyqCheck Pluto output for deprecated API versions before merging.