Skip to content

ci: use specific runner os versions in github actions#9613

Merged
yihau merged 2 commits intoanza-xyz:masterfrom
yihau:remove-latest-tag
Dec 18, 2025
Merged

ci: use specific runner os versions in github actions#9613
yihau merged 2 commits intoanza-xyz:masterfrom
yihau:remove-latest-tag

Conversation

@yihau
Copy link
Member

@yihau yihau commented Dec 17, 2025

Problem

the latest tag might break us unexpectedly

Summary of Changes

use specific versions

@yihau yihau marked this pull request as ready for review December 17, 2025 14:23
@yihau yihau requested a review from a team December 17, 2025 14:23
Copy link

@steviez steviez left a comment

Choose a reason for hiding this comment

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

LGTM assuming you checked that our now pinned versions matched what latest is currently set to

@yihau yihau added this pull request to the merge queue Dec 18, 2025
Merged via the queue into anza-xyz:master with commit b505c80 Dec 18, 2025
41 checks passed
@yihau yihau deleted the remove-latest-tag branch December 18, 2025 02:39
@steviez
Copy link

steviez commented Dec 18, 2025

Shall we BP this one as well for a stronger guarantee of stability on our release branches ?

@yihau
Copy link
Member Author

yihau commented Dec 18, 2025

ah good catch! let's do it!

@yihau yihau added v3.0 Backport to v3.0 branch v3.1 Backport to v3.1 branch labels Dec 18, 2025
@mergify
Copy link

mergify bot commented Dec 18, 2025

Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule.

@mergify
Copy link

mergify bot commented Dec 18, 2025

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.

mergify bot pushed a commit that referenced this pull request Dec 18, 2025
* ci: use specific runner os versions in cargo github actions

* don't use latest tag

(cherry picked from commit b505c80)

# Conflicts:
#	.github/workflows/label-actions.yml
mergify bot pushed a commit that referenced this pull request Dec 18, 2025
* ci: use specific runner os versions in cargo github actions

* don't use latest tag

(cherry picked from commit b505c80)
yihau added a commit that referenced this pull request Dec 22, 2025
… of #9613) (#9636)

ci: use specific runner os versions in github actions (#9613)

* ci: use specific runner os versions in cargo github actions

* don't use latest tag

(cherry picked from commit b505c80)

Co-authored-by: Yihau Chen <yihau.chen@icloud.com>
yihau added a commit that referenced this pull request Dec 22, 2025
… of #9613) (#9635)

* ci: use specific runner os versions in github actions (#9613)

* ci: use specific runner os versions in cargo github actions

* don't use latest tag

(cherry picked from commit b505c80)

# Conflicts:
#	.github/workflows/label-actions.yml

* remove nonexistent workflow file

---------

Co-authored-by: Yihau Chen <yihau.chen@icloud.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v3.0 Backport to v3.0 branch v3.1 Backport to v3.1 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants