Skip to content

chore(deps): update all dependencies#68

Open
renovate[bot] wants to merge 1 commit intodevelopfrom
renovate/all
Open

chore(deps): update all dependencies#68
renovate[bot] wants to merge 1 commit intodevelopfrom
renovate/all

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Sep 3, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Age Confidence
act patch 0.2.810.2.87 age confidence
argocd minor 3.1.13.3.6 age confidence
cookiecutter minor ==2.6.0==2.7.1 age confidence
github-cli minor 2.78.02.89.0 age confidence
golang minor 1.25.01.26.2 age confidence
helm major 3.18.64.1.4 age confidence
hugo minor 0.149.00.160.1 age confidence
kind minor 0.30.00.31.0 age confidence
kubectl minor 1.34.01.35.3 age confidence
kustomize minor 5.7.15.8.1 age confidence
mkdocs-include-markdown-plugin (changelog) minor ==7.1.7==7.2.2 age confidence
mkdocs-material (changelog) minor ==9.6.18==9.7.6 age confidence
nolte/gh-plumbing patch v1.1.11v1.1.12 age confidence
nolte/gh-plumbing action patch v1.1.11v1.1.12 age confidence
packer minor 1.14.11.15.1 age confidence
pre-commit minor ==4.3.0==4.5.1 age confidence
pymdown-extensions minor ==10.16.1==10.21.2 age confidence
python minor 3.13.73.14.4 age confidence
shfmt minor 3.12.03.13.1 age confidence
talhelper minor 3.0.343.1.7 age confidence
talosctl minor 1.11.01.12.6 age confidence
terraform minor 1.13.11.14.8 age confidence
yq minor 4.47.14.52.5 age confidence

Release Notes

nektos/act (act)

v0.2.87

Compare Source

Changelog

Bug fixes
Other
  • 36add66 chore: bump VERSION to 0.2.87

v0.2.86

Compare Source

Changelog

Other
  • e71313c chore: bump VERSION to 0.2.86
  • c28c27e Merge commit from fork
  • 0c739c8 Merge commit from fork
  • 10add23 build(deps): bump GitHub Actions to fix Node.js 20 deprecation (#​6036)

v0.2.85

Compare Source

Changelog

Other
  • 4ea8ec2 chore: bump VERSION to 0.2.85
  • 9e6190d build(deps): bump go.opentelemetry.io/otel/sdk from 1.28.0 to 1.40.0 (#​6014)
  • 77470a0 build(deps): bump github.com/cloudflare/circl from 1.6.1 to 1.6.3 (#​6010)
  • 1030ad2 build(deps): bump github.com/go-git/go-git/v5 from 5.16.2 to 5.16.5 (#​6001)

v0.2.84

Compare Source

Changelog

Bug fixes
Other

v0.2.83

Compare Source

Changelog

Other
  • 6abb867 chore: bump VERSION to 0.2.83
  • e16ac81 chore(mergify) Add merge queue configuration to .mergify.yml (#​5944)

v0.2.82

Compare Source

Changelog

Other
  • 3d71542 chore: bump VERSION to 0.2.82
  • 2f9675f build(deps): bump the dependencies group across 1 directory with 10 updates (#​5935)
argoproj/argo-cd (argocd)

v3.3.6

Compare Source

Quick Start

Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.6/manifests/install.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.6/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes

Full Changelog: argoproj/argo-cd@v3.3.5...v3.3.6

v3.3.5

Compare Source

Quick Start

Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.5/manifests/install.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.5/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes
Dependency updates
Other work

Full Changelog: argoproj/argo-cd@v3.3.4...v3.3.5

v3.3.4

Compare Source

Quick Start

Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.4/manifests/install.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.4/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes
Documentation
Other work

Full Changelog: argoproj/argo-cd@v3.3.3...v3.3.4

v3.3.3

Compare Source

[!IMPORTANT]
Following Helm 3.19.0 change in how Helm interprets K8s cluster version, Argo CD 3.3.3 release contains a change that aligns how Argo CD interprets K8s cluster version with Helm behavior.

Impact: Application Sets with Cluster Generators, that fetch clusters based on their Kubernetes version and use argocd.argoproj.io/auto-label-cluster-info on the cluster secret, need to be updated to use argocd.argoproj.io/kubernetes-version with the vMajor.Minor.Patch format instead of the previous Major.Minor format.

More details here: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#cluster-version-format-change

Quick Start

Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.3/manifests/install.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.3/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes
Other work

Full Changelog: argoproj/argo-cd@v3.3.2...v3.3.3

v3.3.2

Compare Source

[!IMPORTANT]
Before upgrading all types of Argo CD installations to this release, please read the upgrade guide first:
https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#breaking-changes

Upgrading Argo CD which is managing itself

Users who have an Argo CD Application that manages their Argo CD installation, must enable ServerSideApply=true sync option on this Application in order for the upgrade to succeed.

The issue with failed to perform client-side apply migration that existed on version 3.3.0 and 3.3.1 has been solved in this release: #​26279

For users who have previously upgraded to Argo CD 3.3.0or 3.3.1 and applied the temporary remediation of ClientSideApplyMigration=false sync option on the Application that manages their Argo CD, are required to remove this setting to restore the default behavior of performing the migration.
The reason for removing the ClientSideApplyMigration=false sync option is that it may cause conflicts between Argo CD K8s field manager and other field managers at a later point in time.

More details here:
https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#client-side-apply-migration

Quick Start

Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.2/manifests/install.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.2/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes
Documentation

Full Changelog: argoproj/argo-cd@v3.3.1...v3.3.2

v3.3.1

Compare Source

[!IMPORTANT]
Before upgrading all types of Argo CD installations to this release, please read the upgrade guide first:
https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#breaking-changes

Upgrading Argo CD which is managing itself

Users who have an Argo CD Application that manages their Argo CD installation, must enable ServerSideApply=true sync option on this Application in order for the upgrade to succeed.

In some cases, there may be a sync error like Failed to perform client-side apply migration: failed to perform client-side apply migration on manager kubectl-client-side-apply.

We are currently working on a long-term fix to this issue, the progress can be tracked here: #​26279

A temporary remediation is to additionally set the ClientSideApplyMigration=false sync option on this Application. This solution is temporary and not recommended for the long run because it may result in conflicts between Argo CD K8s field manager and other field managers at a later point in time, and if you use it, you will need to remove it after the above issue is fixed.

More details here:
https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#client-side-apply-migration

Quick Start

Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.1/manifests/install.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.1/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes
Dependency updates
Other work

Full Changelog: argoproj/argo-cd@v3.3.0...v3.3.1

v3.3.0

Compare Source

[!IMPORTANT]
Before upgrading all types of Argo CD installations to this release, please read the upgrade guide first:
https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#breaking-changes

Upgrading Argo CD which is managing itself

Users who have an Argo CD Application that manages their Argo CD installation, must enable ServerSideApply=true sync option on this Application in order for the upgrade to succeed.

In some cases, there may be a sync error like Failed to perform client-side apply migration: failed to perform client-side apply migration on manager kubectl-client-side-apply.

We are currently working on a long-term fix to this issue, the progress can be tracked here: #​26279

A temporary remediation is to additionally set the ClientSideApplyMigration=false sync option on this Application. This solution is temporary and not recommended for the long run because it may result in conflicts between Argo CD K8s field manager and other field managers at a later point in time, and if you use it, you will need to remove it after the above issue is fixed.

More details here:
https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#client-side-apply-migration

Quick Start

Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.0/manifests/install.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.0/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post.

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Features

@renovate renovate bot added chore Maintenance dependencies Pull requests that update a dependency file. labels Sep 3, 2025
@renovate renovate bot changed the title chore(deps): update dependency golang to v1.25.1 chore(deps): update all dependencies Sep 4, 2025
@renovate renovate bot force-pushed the renovate/all branch 10 times, most recently from d5f24c2 to 08d3eaf Compare September 10, 2025 18:47
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 68d3cd2 to 051298e Compare September 18, 2025 20:30
@renovate renovate bot force-pushed the renovate/all branch 7 times, most recently from 643c19e to b85f865 Compare September 29, 2025 00:58
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from 97ec222 to df3d20c Compare October 2, 2025 18:41
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from f634163 to b8a3223 Compare October 24, 2025 16:46
@renovate renovate bot force-pushed the renovate/all branch 8 times, most recently from ce55fe3 to a0a344f Compare November 7, 2025 05:06
@renovate renovate bot force-pushed the renovate/all branch 10 times, most recently from 041318d to 74c5fcd Compare November 15, 2025 06:48
@renovate renovate bot force-pushed the renovate/all branch 7 times, most recently from 328d8e9 to cb5c09c Compare November 25, 2025 02:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore Maintenance cicd ci/cd process functionality. dependencies Pull requests that update a dependency file.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants