Bump carvel.dev/kbld from 0.47.3 to 0.49.1 in /hack/kbld

[dependabot]

Bumps carvel.dev/kbld from 0.47.3 to 0.49.1.

Release notes

Sourced from carvel.dev/kbld's releases.

v0.49.1

Installation

By downloading binary from the release

For instance, if you are using Linux on an AMD64 architecture:

# Download the binary
curl -LO https://github.com/carvel-dev/kbld/releases/download/v0.49.1/kbld-linux-amd64
Move the binary in to your PATH
mv kapp-linux-amd64 /usr/local/bin/kbld
Make the binary executable
chmod +x /usr/local/bin/kbld

Via Homebrew (macOS or Linux)

$ brew tap carvel-dev/carvel
$ brew install kbld
$ kbld version  

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:

# Download the checksums file, certificate and signature
curl -LO https://github.com/carvel-dev/kbld/releases/download/v0.49.1/checksums.txt
curl -LO https://github.com/carvel-dev/kbld/releases/download/v0.49.1/checksums.txt.pem
curl -LO https://github.com/carvel-dev/kbld/releases/download/v0.49.1/checksums.txt.sig
Verify the checksums file
cosign verify-blob checksums.txt 
--certificate checksums.txt.pem 
--signature checksums.txt.sig 
--certificate-identity-regexp=https://github.com/carvel-dev 
--certificate-oidc-issuer=https://token.actions.githubusercontent.com

Verify binary integrity

To verify the integrity of the downloaded binary, you can utilize the checksums file after having validated its signature.

</tr></table> 

... (truncated)

Commits

• d633d6d Replace SHA1 usage with SHA256 for enhanced security
• ea02eee Merge pull request #596 from BulldromeQ/jib-support
• 5c2474d test: Revert to original pack builder image
• 80d5824 test: Pin distroless/java17-debian11 base image for maven e2e test
• 6d3625a test: Use updated builder image for pack E2E test
• 40e8db4 test: Move maven-app to separate asset folder
• 82273e9 fix: Address Copilot review comments
• b2fc9ca test: Fix e2e test linter errors
• f92ebc4 Chore: trigger clean CI run
• 138c641 Fix line-length lints in build_maven_jib_test.go
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.27%. Comparing base (67f8728) to head (8d7f0c0).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #589   +/-   ##
=======================================
  Coverage   73.27%   73.27%           
=======================================
  Files          28       28           
  Lines        1474     1474           
=======================================
  Hits         1080     1080           
  Misses        324      324           
  Partials       70       70           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.