Skip to content

chore: bump workspace crate versions to 0.2.2 for release/v0.2.2 - #214

Open
hsliuustc0106 wants to merge 1 commit into
mainfrom
cursor/bump-workspace-crates-0.2.2-437d
Open

hsliuustc0106 wants to merge 1 commit into
mainfrom
cursor/bump-workspace-crates-0.2.2-437d

Conversation

@hsliuustc0106

Copy link
Copy Markdown
Contributor

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.

  1. 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.

  2. What is the highest-leverage variable for that outcome?

    Answer: The package version field 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.

  3. 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.

  4. 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.lock so 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.toml has 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:

  1. Confirm each of the 14 manifests has version = "0.2.2" on the package version line, and that no other Cargo.toml version line changed. omni-kev-native remains 0.1.0.
  2. Regenerate Cargo.lock with Cargo and confirm only the 14 workspace omni-* package versions moved to 0.2.2.
  3. Re-read the lockfile with --locked so a later --locked CI build does not rewrite it.

Test Result

  • cargo +stable metadata --format-version 1 (Rust 1.100.0) updated Cargo.lock. The lockfile diff is 14 version lines, one per listed workspace omni-* package, from 0.2.1 to 0.2.2. Third-party minimal-lexical 0.2.1, windows-link 0.2.1, and foldhash 0.2.0 are unchanged. omni-kev-native stays 0.1.0. No other packages, checksums, or dependency edges changed.
  • cargo +stable metadata --locked --format-version 1 --no-deps exited 0. That metadata lists the 14 bumped omni-* packages at 0.2.2 and omni-kev-native at 0.1.0.

Not run: cargo fmt --all --check, cargo clippy --workspace --locked, cargo test --workspace --locked, and cargo build --workspace --release --locked from .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 f1e674f2d324f5bb4e1ba2162551d0b633f20be0 and head e5b791f21e82e93ff8bb7fa122344394b9a177c4. 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, and Cargo.lock matches those versions. omni-kev-native is not in the diff and remains 0.1.0.

  • I have reviewed the full diff and addressed the issues I found.
  • I have checked that the change follows the project's architecture and stays focused on the stated purpose.
  • I have run the checks appropriate to this change and reported commands, results, and anything I could not verify above.
  • I have checked that the PR description, documentation, and any accuracy or performance claims match the implementation and available evidence.
Open in Web Open in Cursor 

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

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants