chore(deps): update all non-major dependencies #4
Loading…
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.13.1
->v2.13.3
v3.9.2
->v3.9.4
v0.38.0
->v0.39.0
Release Notes
argoproj/argo-cd (quay.io/argoproj/argocd)
v2.13.3
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
f260510
: fix(api): send to closed channel in mergeLogStreams (#7006) (#21178) (#21187) (@gcp-cherry-pick-bot[bot])09eede0
: fix(appset): Fix appset generate in --core mode for cluster gen (#21170) (#21236) (@gcp-cherry-pick-bot[bot])64a14a0
: fix(ui): add optional check to avoid undefined reference in project detail (#20044) (#21263) (@crenshaw-dev)c76a131
: fix: Change applicationset generate HTTP method to avoid route conflicts (#20758) (#21300) (@gcp-cherry-pick-bot[bot])079754c
: fix: Populate destination name when destination server is specified (#21063) (cherry-pick 2.13) (#21176) (@adriananeci)Full Changelog: https://github.com/argoproj/argo-cd/compare/v2.13.2...v2.13.3
v2.13.2
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
ad36916
: fix(cli): Fix appset generate in --core mode (#20717) (#20883) (@gcp-cherry-pick-bot[bot])01ae20d
: fix: 20791 - sync multi-source application out of order source syncs (cherry-pick #21071) (#21077) (@gcp-cherry-pick-bot[bot])831e452
: fix: API server should not attempt to read secrets in all namespaces (#20950) (#20960) (@gcp-cherry-pick-bot[bot])a3624a3
: fix: Allow to delete repos with invalid urls (#20921) (#20975) (#21116) (@gcp-cherry-pick-bot[bot])89ef356
: fix: Bitbucket Cloud PR Author is processed correctly (#20769) (#20990) (#21039) (@gcp-cherry-pick-bot[bot])f8d6665
: fix: Memory leak in repo-server (#20876) (#20894) (@gcp-cherry-pick-bot[bot])b6af657
: fix: add missing fields in listrepositories (#20991) (#21129) (@blakepettersson)Dependency updates
0680ddb
: chore(deps): bump http-proxy-middleware from 2.0.4 to 2.0.7 in /ui (#20518) (#20892) (@gcp-cherry-pick-bot[bot])Full Changelog: https://github.com/argoproj/argo-cd/compare/v2.13.1...v2.13.2
getsops/sops (sops)
v3.9.4
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.9.4.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.9.4
ghcr.io/getsops/sops:v3.9.4-alpine
Quay.io
quay.io/getsops/sops:v3.9.4
quay.io/getsops/sops:v3.9.4-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.9.3...v3.9.4
v3.9.3
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.9.3.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.9.3
ghcr.io/getsops/sops:v3.9.3-alpine
Quay.io
quay.io/getsops/sops:v3.9.3
quay.io/getsops/sops:v3.9.3-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.9.2...v3.9.3
helmfile/vals (vals)
v0.39.0
Compare Source
What's Changed
Full Changelog: https://github.com/helmfile/vals/compare/v0.38.0...v0.39.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.
cb71ee5f4f
tob00579a01e
chore(deps): update quay.io/argoproj/argocd docker tag to v2.13.2to chore(deps): update all non-major dependenciesb00579a01e
to9df2140f06
9df2140f06
tof03286536c
f03286536c
tof58b5a8cd3
Checkout
From your project repository, check out a new branch and test the changes.