Update dependency carvel-dev/kapp to v0.63.3 #374
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.
This PR contains the following updates:
0.60.0
->0.63.3
Release Notes
carvel-dev/kapp (carvel-dev/kapp)
v0.63.3
Compare Source
Installation and signature verification
Installation
By downloading binary from the release
For instance, if you are using Linux on an AMD64 architecture:
Via Homebrew (macOS or Linux)
Verify checksums file signature
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC(Refer this page for cosign installation). 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 checksums.txt --ignore-missing
✨ What's new
Full Changelog: carvel-dev/kapp@v0.63.2...v0.63.3
📂 Files Checksum
v0.63.2
Compare Source
Installation and signature verification
Installation
By downloading binary from the release
For instance, if you are using Linux on an AMD64 architecture:
Via Homebrew (macOS or Linux)
Verify checksums file signature
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC(Refer this page for cosign installation). 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 checksums.txt --ignore-missing
✨ What's new
New Contributors
Full Changelog: carvel-dev/kapp@v0.63.1...v0.63.2
📂 Files Checksum
v0.63.1
Compare Source
Installation and signature verification
Installation
By downloading binary from the release
For instance, if you are using Linux on an AMD64 architecture:
Via Homebrew (macOS or Linux)
Verify checksums file signature
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC(Refer this page for cosign installation). 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 checksums.txt --ignore-missing
✨ What's new
SelfSubjectAccessReview
orSelfSubjectRulesReview
by @everettraven in #931New Contributors
Full Changelog: carvel-dev/kapp@v0.62.0...v0.63.1
📂 Files Checksum
v0.62.1
Compare Source
Installation and signature verification
Installation
By downloading binary from the release
For instance, if you are using Linux on an AMD64 architecture:
Via Homebrew (macOS or Linux)
Verify checksums file signature
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC(Refer this page for cosign installation). 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 checksums.txt --ignore-missing
✨ What's new
Full Changelog: carvel-dev/kapp@v0.62.0...v0.62.1
📂 Files Checksum
v0.62.0
Compare Source
Installation and signature verification
Installation
By downloading binary from the release
For instance, if you are using Linux on an AMD64 architecture:
Via Homebrew (macOS or Linux)
Verify checksums file signature
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC(Refer this page for cosign installation). 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 checksums.txt --ignore-missing
✨ What's new
carvel.dev/kapp
this is a breaking change on this version, no impact for users that only use the binariesFull Changelog: carvel-dev/kapp@v0.61.0...v0.62.0
📂 Files Checksum
v0.61.0
Compare Source
Installation and signature verification
Installation
By downloading binary from the release
For instance, if you are using Linux on an AMD64 architecture:
Via Homebrew (macOS or Linux)
Verify checksums file signature
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC(Refer this page for cosign installation). 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 checksums.txt --ignore-missing
✨ What's new
🔈 Callouts
Full Changelog: carvel-dev/kapp@v0.60.0...v0.61.0
📂 Files Checksum
v0.60.2
Compare Source
Installation and signature verification
Installation
By downloading binary from the release
For instance, if you are using Linux on an AMD64 architecture:
Via Homebrew (macOS or Linux)
Verify checksums file signature
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC(Refer this page for cosign installation). 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 checksums.txt --ignore-missing
✨ What's new
Full Changelog: carvel-dev/kapp@v0.60.1...v0.60.2
📂 Files Checksum
v0.60.1
Compare Source
Installation and signature verification
Installation
By downloading binary from the release
For instance, if you are using Linux on an AMD64 architecture:
Via Homebrew (macOS or Linux)
Verify checksums file signature
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC(Refer this page for cosign installation). 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 checksums.txt --ignore-missing
What's Changed
Full Changelog: carvel-dev/kapp@v0.60.0...v0.60.1
📂 Files Checksum
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.