chore: prepare 0.3 code freeze#177
Merged
Merged
Conversation
github-actions
Bot
added
size:S
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (10)
WalkthroughVersion 0.4.0 release coordinating Rust workspace and Node.js package versions with updated nightly CI branch configuration. Workspace package versions and dependencies bumped from 0.3.0 to 0.4.0, Node.js packages synchronized to 0.4.0, and release/0.3 added to nightly build branches. ChangesRelease 0.4.0 coordination
🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add Comment |
Signed-off-by: Will Killian <wkillian@nvidia.com>
willkill07
force-pushed
the
docs/code-freeze-0.3
branch
from
52ab4ad to
61597aa
Compare
zhongxuanwang-nv
pushed a commit
to zhongxuanwang-nv/NeMo-Relay
that referenced
this pull request
May 29, 2026
#### Overview
Prepare the repository for the 0.3 code freeze by cutting the release branch, moving main to the next development version, and cleaning up current-version documentation references.
- [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.
#### Details
- Created and pushed `release/0.3` from `upstream/main` commit `932248c37e92d2918cde1c545c19662bc8b786bd`.
- Added `release/0.3` to `.github/nightly-alpha-branches.yaml` so nightly alpha tagging covers the frozen branch.
- Ran `just set-version 0.4.0` to bump main release-versioned package surfaces after the branch cut.
- Updated current-version docs examples from `0.3.0` to `0.4.0` for install commands, OpenClaw package examples, and observability service-version examples.
- Updated the code-freeze skill to search documentation source for old release-version references during future freezes.
- Release-bound PRs for 0.3 should now target `release/0.3`; main continues toward `0.4.0`.
Validation:
- `ruby -e 'require "yaml"; YAML.load_file(".github/nightly-alpha-branches.yaml"); YAML.load_file(".github/workflows/nightly-alpha-tag.yaml")'`
- `just set-version 0.4.0`
- `rg -n '0\.3\.0' README.md docs fern --glob '!docs/_build/**' || true` returned no source-doc matches
- `git diff --check`
- `cargo check --workspace`
- `just docs`
- Commit hook changed-file checks
#### Where should the reviewer start?
Start with `.github/nightly-alpha-branches.yaml`, then verify the `0.4.0` version bump in `Cargo.toml`, the package lockfiles, and the docs version-reference updates.
#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)
- Relates to: none
Signed-off-by: Will Killian <wkillian@nvidia.com>
Signed-off-by: Zhongxuan Wang <daniewang@nvidia.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Prepare the repository for the 0.3 code freeze by cutting the release branch, moving main to the next development version, and cleaning up current-version documentation references.
Details
release/0.3fromupstream/maincommit932248c37e92d2918cde1c545c19662bc8b786bd.release/0.3to.github/nightly-alpha-branches.yamlso nightly alpha tagging covers the frozen branch.just set-version 0.4.0to bump main release-versioned package surfaces after the branch cut.0.3.0to0.4.0for install commands, OpenClaw package examples, and observability service-version examples.release/0.3; main continues toward0.4.0.Validation:
ruby -e 'require "yaml"; YAML.load_file(".github/nightly-alpha-branches.yaml"); YAML.load_file(".github/workflows/nightly-alpha-tag.yaml")'just set-version 0.4.0rg -n '0\.3\.0' README.md docs fern --glob '!docs/_build/**' || truereturned no source-doc matchesgit diff --checkcargo check --workspacejust docsWhere should the reviewer start?
Start with
.github/nightly-alpha-branches.yaml, then verify the0.4.0version bump inCargo.toml, the package lockfiles, and the docs version-reference updates.Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)
Summary by CodeRabbit
Chores
Documentation