Repository navigation
chore(deps): bump Go to 1.23.6 - #14484
Conversation
rhybrillou
left a comment
There was a problem hiding this comment.
How about these files ?
.devcontainer/devcontainer.json
.github/workflows/fixxxer.yaml
.openshift-ci/Dockerfile.build_root
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #14484 +/- ##
=======================================
Coverage 49.10% 49.11%
=======================================
Files 2522 2522
Lines 184227 184227
=======================================
+ Hits 90468 90478 +10
+ Misses 86557 86549 -8
+ Partials 7202 7200 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
This change is part of the following stack: Change managed by git-spice. |
|
How about these files ? |
|
/retest |
2b41a5e to
034419d
Compare
Signed-off-by: Tomasz Janiszewski <tomek@redhat.com>
|
Images are ready for the commit at 0ca41db. To use with deploy scripts, first |
porridge
left a comment
There was a problem hiding this comment.
CI does not look too happy 😟
Also, I wonder whether we should have a CI check that does grep -ER stackrox-(build|test)-\d+ and makes sure the version is consistent...
|
I think we may need openshift/release#62496 merged for CI to work. I held that from getting merged until this PR is ready. Feel free to |
|
/retest |
The problem was with disk space not the go version itself :(
I also thought about this and some way of automation around upgrading the go. Maybe instead of having it in the image we can download it at build time (toolchain or even bash download) so we need only 1 PR to bump go instead of 4 |
|
The check could look like this and expected output is 1 |
Description
This PR bumps Go version in builder/test images to allow upgrading cosign:
chore(deps): use upstream cosign instead of fork #14430
CHANGELOG update is not needed
Documentation is not needed
Testing
Automated testing
How I validated my change
CI