chore(deps): bump kbld from v0.48.1 to v0.49.1#1838
Open
nikhilsagotiya wants to merge 1 commit into
Open
Conversation
Signed-off-by: Nikhil Sagotiya <nikjain0594@gmail.com>
nikhilsagotiya
force-pushed
the
bump-kbld-v0.49.1
branch
from
92d5431 to
32597ed
Compare
Author
|
Hi @joaopapereira , Could you please review this PR, Thanks. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What this PR does / why we need it:
Bumps kbld dependency from v0.48.1 to v0.49.1 to pick up the SHA-1 removal fix.
kbld v0.49.1 replaces crypto/sha1 with crypto/sha256 in the e2e packaging test, eliminating a cryptographic audit finding (SHA-1 is not FIPS-approved). Although the SHA-1 usage was in test-only code (//go:build e2e), the upstream fix has been merged and this bump brings kapp-controller in sync with the latest kbld release.
Reference: carvel-dev/kbld#598
Which issue(s) this PR fixes:
Fixes # (no separate issue filed — tracked via the upstream kbld PR above)
Does this PR introduce a user-facing change?
Additional Notes for your reviewer:
Review Checklist:
a link to that PR
change
Additional documentation e.g., Proposal, usage docs, etc.: