chore(deps): update all non-major dependencies #8
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/all-minor-patch"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v2.14.7
->v2.14.8
v3.9.4
->v3.10.1
v0.39.4
->v0.40.1
Release Notes
argoproj/argo-cd (quay.io/argoproj/argocd)
v2.14.8
Compare Source
Quick Start
Non-HA:
HA:
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.
Upgrading
If upgrading from a different minor version, be sure to read the upgrading documentation.
Changelog
Bug fixes
9a9e62d
: fix(server): fully populate app destination before project checks (#22408) (#22426) (@crenshaw-dev)7acdaa9
: fix: CVE-2025-26791 upgrading redoc dep to 2.4.0 to avoid DOMPurify b… (#21997) (@nmirasch)872319e
: fix: handle annotated git tags correctly in repo server cache (#21771) (#22424) (@aali309)Dependency updates
9f832cd
: chore(deps): bump github.com/golang-jwt/jwt to 4.5.2/5.2.2 (#22465) (@crenshaw-dev)Other work
ec45e33
: fix(ui, rbac): project-roles (#21829) (2.14 backport) (#22461) (@blakepettersson)Full Changelog: https://github.com/argoproj/argo-cd/compare/v2.14.7...v2.14.8
getsops/sops (sops)
v3.10.1
Compare Source
Installation
To install
sops
, download one of the pre-built binaries provided for your platform from the artifacts attached to this release.For instance, if you are using Linux on an AMD64 architecture:
Verify checksums file signature
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC. To validate the signature of this file, run the following commands:
Verify binary integrity
To verify the integrity of the downloaded binary, you can utilize the checksums file after having validated its signature:
Verify artifact provenance
The SLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through an in-toto link metadata file named
sops-v3.10.1.intoto.jsonl
. To verify the provenance of an artifact, you can utilize theslsa-verifier
tool:Container Images
The
sops
binaries are also available as container images, based on Debian (slim) and Alpine Linux. The Debian-based container images include any dependencies which may be required to make use of certain key services, such as GnuPG, AWS KMS, Azure Key Vault, and Google Cloud KMS. The Alpine-based container images are smaller in size, but do not include these dependencies.These container images are available for the following architectures:
linux/amd64
andlinux/arm64
.GitHub Container Registry
ghcr.io/getsops/sops:v3.10.1
ghcr.io/getsops/sops:v3.10.1-alpine
Quay.io
quay.io/getsops/sops:v3.10.1
quay.io/getsops/sops:v3.10.1-alpine
Verify container image signature
The container images are signed using Cosign with GitHub OIDC. To validate the signature of an image, run the following command:
Verify container image provenance
The container images include SLSA provenance attestations. For more information around the verification of this, please refer to the
slsa-verifier
documentation.Software Bill of Materials
The Software Bill of Materials (SBOM) for each binary is accessible within the artifacts enclosed with this release. It is presented as an SPDX JSON file, formatted as
<binary>.spdx.sbom.json
.What's Changed
Full Changelog: https://github.com/getsops/sops/compare/v3.10.0...v3.10.1
v3.10.0
Compare Source
Installation
To install
sops
, download one of the pre-built binaries provided for your platform from the artifacts attached to this release.For instance, if you are using Linux on an AMD64 architecture:
Verify checksums file signature
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC. To validate the signature of this file, run the following commands:
Verify binary integrity
To verify the integrity of the downloaded binary, you can utilize the checksums file after having validated its signature:
Verify artifact provenance
The SLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through an in-toto link metadata file named
sops-v3.10.0.intoto.jsonl
. To verify the provenance of an artifact, you can utilize theslsa-verifier
tool:Container Images
The
sops
binaries are also available as container images, based on Debian (slim) and Alpine Linux. The Debian-based container images include any dependencies which may be required to make use of certain key services, such as GnuPG, AWS KMS, Azure Key Vault, and Google Cloud KMS. The Alpine-based container images are smaller in size, but do not include these dependencies.These container images are available for the following architectures:
linux/amd64
andlinux/arm64
.GitHub Container Registry
ghcr.io/getsops/sops:v3.10.0
ghcr.io/getsops/sops:v3.10.0-alpine
Quay.io
quay.io/getsops/sops:v3.10.0
quay.io/getsops/sops:v3.10.0-alpine
Verify container image signature
The container images are signed using Cosign with GitHub OIDC. To validate the signature of an image, run the following command:
Verify container image provenance
The container images include SLSA provenance attestations. For more information around the verification of this, please refer to the
slsa-verifier
documentation.Software Bill of Materials
The Software Bill of Materials (SBOM) for each binary is accessible within the artifacts enclosed with this release. It is presented as an SPDX JSON file, formatted as
<binary>.spdx.sbom.json
.What's Changed
oauth2.TokenSource
in GCP KMS by @matheuscscp in https://github.com/getsops/sops/pull/1794GOOGLE_OAUTH_ACCESS_TOKEN
for Google Cloud Platform by @marensofier in https://github.com/getsops/sops/pull/1578.sops.yml
files found while searching for.sops.yaml
by @felixfontein in https://github.com/getsops/sops/pull/1820New Contributors
Full Changelog: https://github.com/getsops/sops/compare/v3.9.4...v3.10.0
helmfile/vals (vals)
v0.40.1
Compare Source
What's Changed
Full Changelog: https://github.com/helmfile/vals/compare/v0.40.0...v0.40.1
v0.40.0
Compare Source
What's Changed
Full Changelog: https://github.com/helmfile/vals/compare/v0.39.4...v0.40.0
Configuration
📅 Schedule: 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.
e53a7a39f4
to2f7261612f
chore(deps): update quay.io/argoproj/argocd docker tag to v2.14.8to chore(deps): update all non-major dependencies2f7261612f
to3686b5fc1a
Checkout
From your project repository, check out a new branch and test the changes.