chore: update releases #93
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/releases
branch
from
a7cb672 to
3c3f31d
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/releases
branch
from
3c3f31d to
b2a3ac9
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/releases
branch
from
b2a3ac9 to
eccd36e
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/releases
branch
from
eccd36e to
e80dfec
Compare
renovate
bot
force-pushed
the
renovate/releases
branch
from
e80dfec to
3008755
Compare
renovate
bot
force-pushed
the
renovate/releases
branch
2 times, most recently
from
122f3c6 to
7a03aca
Compare
renovate
bot
force-pushed
the
renovate/releases
branch
2 times, most recently
from
c03565d to
77d0804
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/releases
branch
5 times, most recently
from
d3be955 to
9b71427
Compare
renovate
bot
force-pushed
the
renovate/releases
branch
from
9b71427 to
9e698a3
Compare
renovate
bot
force-pushed
the
renovate/releases
branch
4 times, most recently
from
23943f8 to
246614c
Compare
renovate
bot
force-pushed
the
renovate/releases
branch
3 times, most recently
from
5d8fb57 to
f77cc4a
Compare
renovate
bot
force-pushed
the
renovate/releases
branch
4 times, most recently
from
a8474a6 to
5eae75b
Compare
renovate
bot
force-pushed
the
renovate/releases
branch
3 times, most recently
from
efcf6c5 to
36ae388
Compare
renovate
bot
force-pushed
the
renovate/releases
branch
5 times, most recently
from
c545ca9 to
1dbe9d0
Compare
renovate
bot
force-pushed
the
renovate/releases
branch
3 times, most recently
from
16d4f2a to
970d497
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/releases
branch
from
970d497 to
bd5375b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update Request | Renovate Bot
This PR contains the following updates:
2.19.1->2.24.1v0.18.0->v0.20.1v3.9.1->v3.9.4v0.20.2->v0.20.3v4.44.3->v4.45.1v0.17.0->v0.19.0Release Notes
aws/aws-cli (aws/aws-cli)
v2.24.1Compare Source
v2.24.0Compare Source
v2.23.15Compare Source
v2.23.14Compare Source
v2.23.13Compare Source
v2.23.12Compare Source
v2.23.11Compare Source
v2.23.10Compare Source
v2.23.9Compare Source
v2.23.8Compare Source
v2.23.7Compare Source
v2.23.6Compare Source
v2.23.5Compare Source
v2.23.4Compare Source
v2.23.3Compare Source
v2.23.2Compare Source
v2.23.1Compare Source
v2.23.0Compare Source
v2.22.35Compare Source
v2.22.34Compare Source
v2.22.33Compare Source
v2.22.32Compare Source
v2.22.31Compare Source
v2.22.30Compare Source
v2.22.29Compare Source
v2.22.28Compare Source
v2.22.27Compare Source
v2.22.26Compare Source
v2.22.25Compare Source
v2.22.24Compare Source
v2.22.23Compare Source
v2.22.22Compare Source
v2.22.21Compare Source
v2.22.20Compare Source
v2.22.19Compare Source
v2.22.18Compare Source
v2.22.17Compare Source
v2.22.16Compare Source
v2.22.15Compare Source
v2.22.14Compare Source
v2.22.13Compare Source
v2.22.12Compare Source
v2.22.11Compare Source
v2.22.10Compare Source
v2.22.9Compare Source
v2.22.8Compare Source
v2.22.7Compare Source
v2.22.6Compare Source
v2.22.5Compare Source
v2.22.4Compare Source
v2.22.3Compare Source
v2.22.2Compare Source
v2.22.1Compare Source
v2.22.0Compare Source
v2.21.3Compare Source
v2.21.2Compare Source
v2.21.1Compare Source
v2.21.0Compare Source
v2.20.0Compare Source
v2.19.5Compare Source
v2.19.4Compare Source
v2.19.3Compare Source
v2.19.2Compare Source
docker/buildx (docker/buildx)
v0.20.1Compare Source
Welcome to the v0.20.1 release of buildx!
Please try out the release binaries and report any issues at
https://github.com/docker/buildx/issues.
Contributors
Notable Changes
bake --printoutput missing some attributes for attestations #2937Dependency Changes
This release has no dependency changes
Previous release can be found at v0.20.0
v0.20.0Compare Source
Welcome to the v0.20.0 release of buildx!
Please try out the release binaries and report any issues at
https://github.com/docker/buildx/issues.
Contributors
Notable Changes
buildx historycommand has been added that allows working with build records of completed and running builds. You can use these commands to list, inspect, remove your builds, replay the logs of already completed builds, and quickly open your builds in Docker Desktop Build UI for further debugging. This is an early version of this command and we expect to add more features in the future releases. #2891 #2925BUILDX_BAKE_ENTITLEMENTS_FS=0#2875--listflag to list targets and variables #2900 #2907quietprogress mode #2899Dependency Changes
ced1acd->e8a1dd7a090f58->c51673e5ac0b6anew31cf1f4->b14e27ff6361c8->5fefd90f6361c8->324edc32dd684a->70dd3763b25d92->18e509bPrevious release can be found at v0.19.3
v0.19.3Compare Source
Welcome to the v0.19.3 release of buildx!
Please try out the release binaries and report any issues at
https://github.com/docker/buildx/issues.
Contributors
Notable changes
--set#2861Dependency Changes
This release has no dependency changes
Previous release can be found at v0.19.2
v0.19.2Compare Source
Welcome to the v0.19.2 release of buildx!
Please try out the release binaries and report any issues at
https://github.com/docker/buildx/issues.
Notable changes
--setflag to avoid the need to allow the same path multiple times #2834Dependency Changes
This release has no dependency changes
Previous release can be found at v0.19.1
v0.19.1Compare Source
buildx 0.19.1
Welcome to the v0.19.1 release of buildx!
Please try out the release binaries and report any issues at
https://github.com/docker/buildx/issues.
Notable Changes
Dependency Changes
This release has no dependency changes
Previous release can be found at v0.19.0
v0.19.0Compare Source
buildx 0.19.0
Welcome to the v0.19.0 release of buildx!
Please try out the release binaries and report any issues at
https://github.com/docker/buildx/issues.
Contributors
Notable Changes
--allowwhen your build needs to read or write files outside of your current working directory. This feature currently only reports a warning when using local Bake definition, but will start to produce an error starting from the v0.20 release. If you wish to enable the error in the current release, you can setBUILDX_BAKE_ENTITLEMENTS_FS=1#2796 #2812Dependency Changes
397af53->31cf1f4ef581f9->f6361c8ef581f9->f6361c8Previous release can be found at v0.18.0
getsops/sops (getsops/sops)
v3.9.4Compare 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 the binary using the checksums file sha256sum -c sops-v3.9.4.checksums.txt --ignore-missingVerify 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-verifiertool:Container Images
The
sopsbinaries 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/amd64andlinux/arm64.GitHub Container Registry
ghcr.io/getsops/sops:v3.9.4ghcr.io/getsops/sops:v3.9.4-alpineQuay.io
quay.io/getsops/sops:v3.9.4quay.io/getsops/sops:v3.9.4-alpineVerify 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-verifierdocumentation.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: getsops/sops@v3.9.3...v3.9.4
v3.9.3Compare 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 the binary using the checksums file sha256sum -c sops-v3.9.3.checksums.txt --ignore-missingVerify 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-verifiertool:Container Images
The
sopsbinaries 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/amd64andlinux/arm64.GitHub Container Registry
ghcr.io/getsops/sops:v3.9.3ghcr.io/getsops/sops:v3.9.3-alpineQuay.io
quay.io/getsops/sops:v3.9.3quay.io/getsops/sops:v3.9.3-alpineVerify 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-verifierdocumentation.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: getsops/sops@v3.9.2...v3.9.3
v3.9.2Compare 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 the binary using the checksums file sha256sum -c sops-v3.9.2.checksums.txt --ignore-missingVerify 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.2.intoto.jsonl. To verify the provenance of an artifact, you can utilize theslsa-verifiertool:Container Images
The
sopsbinaries 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/amd64andlinux/arm64.GitHub Container Registry
ghcr.io/getsops/sops:v3.9.2ghcr.io/getsops/sops:v3.9.2-alpineQuay.io
quay.io/getsops/sops:v3.9.2quay.io/getsops/sops:v3.9.2-alpineVerify 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-verifierdocumentation.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
New Contributors
Full Changelog: getsops/sops@v3.9.1...v3.9.2
google/go-containerregistry (google/go-containerregistry)
v0.20.3Compare Source
What's Changed
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.