Skip to content

[YUNIKORN-3144] Update go repro version for image builds#991

Closed
pohanhuang wants to merge 2 commits intoapache:masterfrom
pohanhuang:YUNIKORN-3144
Closed

[YUNIKORN-3144] Update go repro version for image builds#991
pohanhuang wants to merge 2 commits intoapache:masterfrom
pohanhuang:YUNIKORN-3144

Conversation

@pohanhuang
Copy link
Contributor

@pohanhuang pohanhuang commented Nov 22, 2025

What is this PR for?

Bump the go repro version to 1.25.3 to avoid CVEs.

What type of PR is it?

  • - Bug Fix
  • - Improvement
  • - Feature
  • - Documentation
  • - Hot Fix
  • - Refactoring

Todos

  • - Task

What is the Jira issue?

How should this be tested?

Screenshots (if appropriate)

Questions:

  • - The licenses files need update.
  • - There is breaking changes for older versions.
  • - It needs documentation.

Signed-off-by: hhcs9527 <hhcs9527@gmail.com>
@codecov
Copy link

codecov bot commented Nov 23, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 66.16%. Comparing base (b9b4edd) to head (e4ad2d1).
⚠️ Report is 6 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #991      +/-   ##
==========================================
+ Coverage   65.93%   66.16%   +0.22%     
==========================================
  Files          72       72              
  Lines        9307     7723    -1584     
==========================================
- Hits         6137     5110    -1027     
+ Misses       2959     2400     -559     
- Partials      211      213       +2     

☔ View full report in Codecov by Sentry.
📢 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.

Copy link
Contributor

@wilfred-s wilfred-s left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we move to the latest 1.25.5 (due out early next week) as the latest at this moment?

@@ -1 +1 @@
1.23.7
1.25.3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we move to the latest 1.25.5 instead?

@pbacsko
Copy link
Contributor

pbacsko commented Dec 1, 2025

Let's wait until 1.25.5 comes out then we can proceed to close this PR.

@pbacsko
Copy link
Contributor

pbacsko commented Dec 3, 2025

1.25.5 is officially out. @pohanhuang you can change the patch from 1.25.3 to 1.25.5.

@pohanhuang
Copy link
Contributor Author

Will do, thanks for reminding

Signed-off-by: hhcs9527 <hhcs9527@gmail.com>
@pohanhuang
Copy link
Contributor Author

Hi @pbacsko @mitdesai @wilfred-s
I just update the repro version to 1.25.5, please help review, thanks

@pbacsko pbacsko closed this in dd968d6 Dec 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants