Skip to content

[libcxx] Bump Container Runner Version #147831

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 9, 2025
Merged

[libcxx] Bump Container Runner Version #147831

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion libcxx/utils/ci/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ services:
dockerfile: Dockerfile
target: actions-builder
args:
BASE_IMAGE: ghcr.io/actions/actions-runner:2.322.0
BASE_IMAGE: ghcr.io/actions/actions-runner:2.326.0
Copy link
Member

Choose a reason for hiding this comment

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

Should we maybe just use "latest" here?

I don't feel too strongly one way or the other. One approach makes the container build more deterministic but the other requires less maintenance.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'd prefer to keep the version pinned just for reproducibility. I'll probably change how this is wired up at some point too to make upgrading the runner version less of a pain (so that we only touch the runner and not everything else).

<<: *compiler_versions

android-buildkite-builder:
Expand Down
Loading