Skip to content

chore(deps): update dependency siderolabs/talos to v1.13.6 - #2662

Merged
botantler-1[bot] merged 2 commits into
mainfrom
renovate/siderolabs-talos-1.x
Jul 16, 2026
Merged

botantler-1[bot] merged 2 commits into
mainfrom
renovate/siderolabs-talos-1.x

Conversation

@renovate

@renovate renovate Bot commented Jul 16, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
siderolabs/talos patch 1.13.5 → 1.13.6

Release Notes

siderolabs/talos (siderolabs/talos)

v1.13.6

Compare Source

Talos 1.13.6 (2026-07-09)

Welcome to the v1.13.6 release of Talos!

Please try out the release binaries and report any issues at
https://github.com/siderolabs/talos/issues.

Component Updates

Linux: 6.18.38

Talos is built with Go 1.26.5.

Contributors
  • Andrey Smirnov
  • Mateusz Urbanek
  • Noel Georgi
  • Maja Bojarska
  • Mark Glants
Changes
15 commits

Changes from siderolabs/gen
1 commit

Changes from siderolabs/pkgs
7 commits

Changes from siderolabs/tools
1 commit

Dependency Changes
  • github.com/Azure/azure-sdk-for-go/sdk/azcore v1.21.0 -> v1.21.1
  • github.com/aws/aws-sdk-go-v2 v1.41.4 -> v1.41.7
  • github.com/aws/aws-sdk-go-v2/config v1.32.12 -> v1.32.17
  • github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.18.20 -> v1.18.23
  • github.com/aws/aws-sdk-go-v2/service/kms v1.50.3 -> v1.51.1
  • github.com/aws/smithy-go v1.24.2 -> v1.25.1
  • github.com/siderolabs/gen v0.8.6 -> v0.8.7
  • github.com/siderolabs/pkgs v1.13.0-36-g6b315f7 -> v1.13.0-43-gd8c80cc
  • github.com/siderolabs/talos/pkg/machinery v1.13.5 -> v1.13.6
  • github.com/siderolabs/tools v1.13.0-6-g9b78252 -> v1.13.0-7-gc58afd5
  • github.com/sigstore/cosign/v3 v3.0.5 -> v3.0.6
  • github.com/sigstore/sigstore v1.10.5 -> v1.10.6
  • go.uber.org/zap v1.27.1 -> v1.28.0

Previous release can be found at v1.13.5

Images

ghcr.io/siderolabs/flannel:v0.28.5
registry.k8s.io/coredns/coredns:v1.14.2
registry.k8s.io/etcd:v3.6.12
registry.k8s.io/pause:3.10.1
registry.k8s.io/kube-apiserver:v1.36.2
registry.k8s.io/kube-controller-manager:v1.36.2
registry.k8s.io/kube-scheduler:v1.36.2
registry.k8s.io/kube-proxy:v1.36.2
ghcr.io/siderolabs/kubelet:v1.36.2
registry.k8s.io/networking/kube-network-policies:v1.0.0
ghcr.io/siderolabs/installer:v1.13.6
ghcr.io/siderolabs/installer-base:v1.13.6
ghcr.io/siderolabs/imager:v1.13.6
ghcr.io/siderolabs/talos:v1.13.6
ghcr.io/siderolabs/talosctl-all:v1.13.6
ghcr.io/siderolabs/overlays:v1.13.6
ghcr.io/siderolabs/extensions:v1.13.6

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@botantler-1
botantler-1 Bot enabled auto-merge July 16, 2026 08:24
The talosctl ordering test hard-coded TALOS_VERSION: "1.13.5", so every
Talos bump renovate proposes failed CI on an assertion incidental to what
the test actually covers (setup ordering).

Derive the expected version from spec.cluster.talos.version in
ksail.prod.yaml -- the source of truth the workflow comments already name --
following the existing KSAIL_OPERATOR_VERSION idiom. The drift guard now
also catches ksail.prod.yaml and the workflows disagreeing, which a pinned
literal could not.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@botantler-1
botantler-1 Bot added this pull request to the merge queue Jul 16, 2026
@renovate

renovate Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@devantler

Copy link
Copy Markdown
Contributor

🤖 Generated by the Daily AI Engineer

@codex review

Context: renovate's Talos v1.13.5 → v1.13.6 bump failed CI because scripts/tests/test_refresh_flux_ghcr_auth.py hard-coded TALOS_VERSION: "1.13.5" in an assertion incidental to what that test covers (talosctl setup ordering) — so every Talos bump broke. I pushed one adaptation commit deriving the expected version from spec.cluster.talos.version in ksail.prod.yaml (the source of truth the workflow comments already name), following the file's existing KSAIL_OPERATOR_VERSION idiom.

Please focus on whether the drift guard is still meaningful — i.e. that it would still fail if ksail.prod.yaml and the workflows disagreed, rather than passing vacuously.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 22f2e7c683

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +1453 to +1455
self.assertIn(
f'TALOS_VERSION: "{KSAIL_PROD_TALOS_VERSION}"', setup_step
)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Cover the CI talosctl pin in the drift guard

If .github/workflows/ci.yaml's validate-talos TALOS_VERSION is left on an older Talos release while ksail.prod.yaml and the deploy/DR paths are bumped, this test still passes because it only reads ACTION and DR_REBUILD. That leaves the PR-event machine-config validation running a different talosctl than the production pin without this guard catching the drift; include CI_WORKFLOW's setup step here, or add a separate assertion against KSAIL_PROD_TALOS_VERSION.

Useful? React with 👍 / 👎.

Comment thread ksail.prod.yaml
# Pin Talos to match the ISO so 'ksail cluster update' doesn't attempt
# an unwanted in-place upgrade to ksail's default version.
version: v1.13.5
version: v1.13.6

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3 Badge Update the manual DR talosctl pin

When GitHub Actions is unavailable and an operator follows the manual DR rebuild in docs/dr/runbook.md, it still instructs them to use the prod-pinned v1.13.5 talosctl even though this line moves prod to v1.13.6. That leaves the emergency path using a different Talos client than the deploy/DR workflows for the GHCR bridge's Talos API calls; update the runbook to match or derive from this pin.

Useful? React with 👍 / 👎.

Merged via the queue into main with commit 0f46ec8 Jul 16, 2026
17 checks passed
@botantler-1
botantler-1 Bot deleted the renovate/siderolabs-talos-1.x branch July 16, 2026 10:38
@github-project-automation github-project-automation Bot moved this from 🫴 Ready to ✅ Done in 🌊 Project Board Jul 16, 2026
@botantler-1

botantler-1 Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 1.117.4 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@botantler-1 botantler-1 Bot added the released label Jul 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

1 participant