Repository navigation
chore: bump workspace crate versions to 0.2.2 for release/v0.2.2 - #214
Open
hsliuustc0106 wants to merge 1 commit into
Open
hsliuustc0106 wants to merge 1 commit into
hsliuustc0106 wants to merge 1 commit into
Conversation
Bump the 14 existing 0.2.1 workspace package versions to 0.2.2 and refresh Cargo.lock so those omni-* packages resolve at 0.2.2. omni-kev-native stays 0.1.0. Co-authored-by: Hongsheng Liu <liuhongsheng4@huawei.com>
This branch has not been deployed
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
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.
Required human contributor answers
Answer every question before implementation and PR submission, including drafts.
Reuse explicit, still-applicable human answers with a traceable source reference;
ask the human for anything missing and wait. An agent must not invent answers.
Blank fields, placeholders, or an agent-written rationale do not satisfy this gate.
Share only information and source links appropriate for this PR's audience.
What outcome are you trying to achieve?
Answer: Open a non-draft PR that bumps the 14 existing workspace crate versions from 0.2.1 to 0.2.2 for the upcoming release/v0.2.2 cut. Source: Hongsheng approved opening this bump PR on 2026-11-20 ("做 v0.2.2(先开 bump PR)" / "切"). The tag and GitHub Release are not part of this PR.
What is the highest-leverage variable for that outcome?
Answer: The package
versionfield of each listed 0.2.1 workspace Cargo.toml, plus a Cargo-generated Cargo.lock refresh so those omni-* packages resolve at 0.2.2. Source: the same task, which names each crate and file.How will this work move that variable rather than create busywork?
Answer: Each listed package version moves from "0.2.1" to "0.2.2", and cargo rewrites only the matching workspace entries in Cargo.lock. omni-kev-native stays 0.1.0. This PR does not create the tag or the GitHub Release. Source: the same task.
Who is the customer or user, and what do they actually need?
Answer: The release cut on current main. They need the 14 existing 0.2.1 workspace crates at 0.2.2 with Cargo.lock refreshed, as a non-draft PR to main. omni-kev-native remains 0.1.0. Source: the same task.
After answering the four questions: is a PR needed at all to achieve this outcome?
Human decision and rationale (or explicit source reference): Yes. Source: the same task ("After those questions: yes, a PR is needed.").
For a bug fix: link actual observed failure evidence.
Include the observed result of a minimal reproduction, failing regression test,
or relevant trace. Label untested diagnoses as unverified. For a non-bugfix,
state why this is not applicable.
Evidence: Not applicable. This is a package-version bump for the release cut, not a bug fix.
Purpose
Bump the 14 existing workspace crate package versions from 0.2.1 to 0.2.2 and refresh
Cargo.lockso the upcoming release/v0.2.2 cut is based on 0.2.2 packages. Same process as #203. The cut comparison is release/v0.2.1...main. The tag and the GitHub Release are not part of this PR.Updated package versions:
omni-jev(src/frontend/Cargo.toml)omni-runtime(src/runtime/Cargo.toml)omni-clm(src/models/clm/Cargo.toml)omni-cua-s1-native(src/models/cua_s1/native/Cargo.toml)omni-qwen3-5-native(src/models/qwen3_5/native/Cargo.toml)omni-open-jev-native(src/models/open_jev/native/Cargo.toml)omni-jev-vl-native(src/models/jev_vl/native/Cargo.toml)omni-omnijev-native(src/models/omnijev/native/Cargo.toml)omni-laya(src/models/laya/Cargo.toml)omni-cuda(src/backends/cuda/Cargo.toml)omni-decider-native(src/models/decider/native/Cargo.toml)omni-jemm-native(src/models/jemm/native/Cargo.toml)omni-startlux-native(src/models/startlux/native/Cargo.toml)omni-clef(src/models/clef/native/Cargo.toml)omni-kev-native(src/models/kev/native/Cargo.toml) stays at 0.1.0. It is a new workspace member added after v0.2.1 (export/head only; the full native worker is still in draft #197).Root
Cargo.tomlhas no package version and is unchanged. Docs, CI, and source are unchanged. No tag and no GitHub Release are created here.Test Plan
System1-Omni Version / Commit:
f1e674f2d324f5bb4e1ba2162551d0b633f20be0(origin/main, squash-merge of Add a Valen-Decision-1.5 reference worker #204)e5b791f21e82e93ff8bb7fa122344394b9a177c4version = "0.2.2"on the package version line, and that no otherCargo.tomlversion line changed.omni-kev-nativeremains0.1.0.Cargo.lockwith Cargo and confirm only the 14 workspaceomni-*package versions moved to 0.2.2.--lockedso a later--lockedCI build does not rewrite it.Test Result
cargo +stable metadata --format-version 1(Rust 1.100.0) updatedCargo.lock. The lockfile diff is 14 version lines, one per listed workspaceomni-*package, from0.2.1to0.2.2. Third-partyminimal-lexical0.2.1,windows-link0.2.1, andfoldhash0.2.0are unchanged.omni-kev-nativestays0.1.0. No other packages, checksums, or dependency edges changed.cargo +stable metadata --locked --format-version 1 --no-depsexited 0. That metadata lists the 14 bumpedomni-*packages at0.2.2andomni-kev-nativeat0.1.0.Not run:
cargo fmt --all --check,cargo clippy --workspace --locked,cargo test --workspace --locked, andcargo build --workspace --release --lockedfrom.github/workflows/ci.yml. This diff does not change Rust source. Those checks remain for CI.Demo / evidence
N/A. This change only updates package version strings and the generated lockfile. There is no accuracy, latency, throughput, or parity claim, and no user-visible runtime behavior to record.
Self-review
Reviewed base
f1e674f2d324f5bb4e1ba2162551d0b633f20be0and heade5b791f21e82e93ff8bb7fa122344394b9a177c4. The merge-base diff is 15 files, 28 insertions and 28 deletions. Authored application code is 0 lines; the change is manifest and lockfile version fields only. Working tree is clean. No findings in the diff: each edit is the requested package version, andCargo.lockmatches those versions.omni-kev-nativeis not in the diff and remains0.1.0.