-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌱 improve hack/verify-release.sh script #1691
🌱 improve hack/verify-release.sh script #1691
Conversation
53b4303
to
506c1b0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test run locally and it is working as expected.
LGTM
506c1b0
to
11d5745
Compare
Few improvements from previous minor release cycle: - add missing k8s.io/apiserver to module sync - change artefact to artifact for more common spelling - match container image detection from release notes to match the earlier change in the release tooling - rename some of the titles to be more descriptive - mutate go.mod files for osv-scanner so it can accurately report vulnerablities in golang stdlib (ie. mutate "go 1.21" directive to "go 1.21.9" with patch version read off from main Dockerfile - check version of osv-scanner, <1.5.0 give weird warnings now - make docker pull gcrane and osv-scanner images always, so it uses the newest versions Signed-off-by: Tuomo Tanskanen <tuomo.tanskanen@est.tech>
11d5745
to
fa112c8
Compare
Added version check for some tools, otherwise they'll give confusing output. osv-scanner minimum version is 1.5.0. PTAL again. |
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
@adilGhaffarDev: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adilGhaffarDev, lentzi90 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
/ok-to-test |
/override metal3-bmo-e2e-test-pull metal3-centos-e2e-integration-test-main |
@tuminoid: Overrode contexts on behalf of tuminoid: metal3-bmo-e2e-test-pull, metal3-centos-e2e-integration-test-main In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retitle 🌱 improve hack/verify-release.sh script |
/cherry-pick release-0.6 0.5 needs manual cherrypick. |
@tuminoid: new pull request created: #1697 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-0.5 |
@tuminoid: new pull request created: #1698 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Few improvements from previous minor release cycle:
This will be cherry-picked to 0.6 and 0.5 after it merges here as it affects patch release checks.