Skip to content

chore(deps): update asdf (major)#36

Open
goraxe wants to merge 1 commit intomasterfrom
renovate/major-asdf
Open

chore(deps): update asdf (major)#36
goraxe wants to merge 1 commit intomasterfrom
renovate/major-asdf

Conversation

@goraxe
Copy link
Owner

@goraxe goraxe commented May 5, 2024

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change Age Confidence
argocd major 2.9.63.3.2 age confidence
cosign major 2.2.23.0.5 age confidence
helm major 3.13.34.1.1 age confidence
mimirtool major 2.16.03.0.3 age confidence
node (source) major 20.11.024.14.0 age confidence
pnpm (source) major 8.15.110.31.0 age confidence

Release Notes

argoproj/argo-cd (argocd)

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
Bug fixes

@goraxe goraxe force-pushed the renovate/major-asdf branch from ed7fb71 to 9237871 Compare May 6, 2024 10:41
@goraxe goraxe force-pushed the renovate/major-asdf branch 2 times, most recently from bcef695 to c4afa64 Compare May 30, 2024 12:01
@goraxe goraxe force-pushed the renovate/major-asdf branch 2 times, most recently from 96993ba to f91bdcd Compare June 10, 2024 12:46
@goraxe goraxe force-pushed the renovate/major-asdf branch from f91bdcd to 2017890 Compare June 20, 2024 11:16
@goraxe goraxe force-pushed the renovate/major-asdf branch from 2017890 to f4825c9 Compare July 7, 2024 20:52
@goraxe goraxe force-pushed the renovate/major-asdf branch 2 times, most recently from b0ffe3e to 3a5d910 Compare July 22, 2024 00:25
@goraxe goraxe force-pushed the renovate/major-asdf branch 2 times, most recently from c5ce6e6 to 76b759c Compare August 14, 2024 15:32
@goraxe goraxe force-pushed the renovate/major-asdf branch 2 times, most recently from 7b696a8 to fe3f732 Compare August 27, 2024 07:09
@goraxe goraxe force-pushed the renovate/major-asdf branch from fe3f732 to d81e185 Compare September 9, 2024 22:24
@goraxe goraxe force-pushed the renovate/major-asdf branch from d81e185 to 9a1fadf Compare September 20, 2024 15:01
@goraxe goraxe force-pushed the renovate/major-asdf branch 2 times, most recently from 864707c to 2b0f5b7 Compare October 8, 2024 18:05
@goraxe goraxe force-pushed the renovate/major-asdf branch from 2b0f5b7 to 6c6521c Compare October 16, 2024 17:19
@goraxe goraxe force-pushed the renovate/major-asdf branch 2 times, most recently from 8e9f55c to 22dddf2 Compare October 29, 2024 18:01
@goraxe goraxe changed the title chore(deps): update dependency pnpm to v9 chore(deps): update asdf (major) Oct 29, 2024
@goraxe goraxe force-pushed the renovate/major-asdf branch 2 times, most recently from 6279c6f to bf984e5 Compare January 21, 2025 17:54
@goraxe goraxe force-pushed the renovate/major-asdf branch 3 times, most recently from 7e9358a to dda2480 Compare February 6, 2025 19:40
@goraxe goraxe force-pushed the renovate/major-asdf branch 4 times, most recently from 5a08383 to 84c90c6 Compare February 16, 2025 22:00
@goraxe goraxe force-pushed the renovate/major-asdf branch 2 times, most recently from 200150d to 18aa3dd Compare May 15, 2025 03:35
@goraxe goraxe force-pushed the renovate/major-asdf branch 3 times, most recently from 7db8c96 to 02b1c81 Compare May 21, 2025 19:10
@goraxe goraxe force-pushed the renovate/major-asdf branch 3 times, most recently from 9989055 to 91b0425 Compare June 2, 2025 14:03
@goraxe goraxe force-pushed the renovate/major-asdf branch 2 times, most recently from d28e2ba to 70e3f54 Compare June 9, 2025 23:13
@goraxe goraxe force-pushed the renovate/major-asdf branch from 70e3f54 to e176e3b Compare July 23, 2025 04:26
@goraxe goraxe force-pushed the renovate/major-asdf branch from e176e3b to 825a0e2 Compare August 1, 2025 01:27
@goraxe goraxe force-pushed the renovate/major-asdf branch 4 times, most recently from a3e90cf to dd45b65 Compare September 18, 2025 19:34
@goraxe goraxe force-pushed the renovate/major-asdf branch 2 times, most recently from 12262eb to 4d23d41 Compare September 24, 2025 14:02
@goraxe goraxe force-pushed the renovate/major-asdf branch 3 times, most recently from 6c54bfa to 8afa491 Compare October 6, 2025 13:12
@goraxe goraxe force-pushed the renovate/major-asdf branch 4 times, most recently from c465dad to 71f37ed Compare October 14, 2025 10:18
@goraxe goraxe force-pushed the renovate/major-asdf branch from 71f37ed to 90aef27 Compare November 12, 2025 23:25
@goraxe goraxe force-pushed the renovate/major-asdf branch from 90aef27 to 957880b Compare December 15, 2025 00:04
@goraxe goraxe force-pushed the renovate/major-asdf branch 2 times, most recently from dd1bb07 to 7080cb3 Compare February 11, 2026 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants