Skip to content

fix(release): align bundled CLI version with wheels - #4209

Open
ousugo wants to merge 1 commit into
volcengine:mainfrom
ousugo:fix/release-wheel-cli-version
Open

fix(release): align bundled CLI version with wheels#4209
ousugo wants to merge 1 commit into
volcengine:mainfrom
ousugo:fix/release-wheel-cli-version

Conversation

@ousugo

@ousugo ousugo commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Summary

  • pass the published release tag into the reusable distribution workflow
  • configure one validated version for Python packages and the bundled Rust CLI while preserving SCM-derived development versions for manual builds
  • verify installed wheel metadata, openviking.__version__, and the bundled CLI version on every wheel platform
  • allow ov --version and ov -V to run before first-use language configuration

Root cause

The release workflow resolved the Rust CLI version after dependency setup had made the checkout dirty, but built Python wheel metadata after cleaning the checkout. The two build stages therefore derived different versions from the same release commit.

Validation

  • actionlint .github/workflows/_build.yml .github/workflows/release.yml
  • python -m pytest -o addopts= tests/misc/test_release_tag_selection.py -q
  • cargo test -p ov_cli tests::version_flags_render_before_language_setup -- --exact --nocapture
  • cargo build --release -p ov_cli
  • fresh configuration: target/release/ov.exe --version outputs openviking 0.4.16
  • git diff --check upstream/main

Closes #4208

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

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

[Bug]: Release wheels embed next-patch .dev0 in bundled Rust CLI while package metadata uses the release version

1 participant