feat: upgrade intermedidate

[georgehao]

Purpose or design rationale of this PR

Describe your change. Make sure to answer these three questions: What does this PR do? Why does it do it? How does it do it?

PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
• ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
• docs: Documentation-only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

Deployment tag versioning

Has tag in common/version.go been updated or have you added bump-version label to this PR?

• No, this PR doesn't involve a new deployment, git tag, docker image tag
• Yes

Breaking change label

Does this PR have the breaking-change label?

• No, this PR is not a breaking change
• Yes

Summary by CodeRabbit

• Chores
  • Updated the build environment to use newer versions of Rust (nightly-2025-02-14) and Go (1.22.12).
  • Added the latest Rust nightly version as an option when manually triggering the workflow.

[coderabbitai]

Walkthrough

This update adds the Rust nightly version nightly-2025-02-14 as a selectable option in the GitHub Actions workflow and updates the coordinator API Dockerfile to use this Rust version along with a newer Go version (1.22.12). No other build steps or commands are changed.

Changes

File(s)	Change Summary
.github/workflows/intermediate-docker.yml	Added nightly-2025-02-14 to the list of selectable Rust versions in workflow input options.
build/dockerfiles/coordinator-api.Dockerfile	Updated base image tags to use Rust nightly-2025-02-14 and Go 1.22.12.

Possibly related PRs

• upgrade intermediate rust version #1653: Updates the workflow to add a newer Rust nightly version option, directly related to the same workflow file.
• upgrade intermdiate rust to 1.86.0 #1654: Modifies Rust version options in the workflow input, updating selectable toolchain versions.

Suggested reviewers

• Thegaram
• colinlyguo

Poem

A Dockerfile hops to something new,
With Rust and Go, the versions grew.
The workflow’s list now shines so bright,
Welcoming a fresh Rust nightly light.
In the warren, builds run with glee—
Code and carrots, all bug-free! 🥕

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

build/dockerfiles/coordinator-api.Dockerfile (1)

2-2: Hard-coded tag couples Go & Rust upgrades – extract to ARG to keep future bumps trivial

Embedding the full tag string forces every future version bump to touch every stage line.
Consider:

-FROM scrolltech/cuda-go-rust-builder:cuda-11.7.1-go-1.22.12-rust-nightly-2025-02-14 as chef
+ARG BASE_TAG="cuda-11.7.1-go-1.22.12-rust-nightly-2025-02-14"
+FROM scrolltech/cuda-go-rust-builder:${BASE_TAG} as chef

and reuse ${BASE_TAG} in stage base. This keeps the file DRY and reduces merge conflicts when versions change again.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a776ca7 and 5e8f427.

📒 Files selected for processing (2)

• .github/workflows/intermediate-docker.yml (1 hunks)
• build/dockerfiles/coordinator-api.Dockerfile (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: tests

🔇 Additional comments (2)

.github/workflows/intermediate-docker.yml (1)

24-29: New Rust nightly added – please verify image availability & consider bumping the default

nightly-2025-02-14 is now selectable, but the default remains nightly-2023-12-03.

1. Ensure the corresponding intermediate images are already pushed (scrolltech/*:rust-nightly-2025-02-14, etc.); otherwise CI builds depending on the new Dockerfile will fail.
2. If the intention is to standardise on the newer toolchain, update default: to the same version to avoid accidental drift.

build/dockerfiles/coordinator-api.Dockerfile (1)

28-28: Verify that the new base image is present in the registry before merging

scrolltech/cuda-go-rust-builder:cuda-11.7.1-go-1.22.12-rust-nightly-2025-02-14 must exist prior to building coordinator-api, otherwise CI will break early.
Confirm the intermediate-docker workflow publishes this tag or push it manually first.