chore: sync crate version 0.41.0 -> 0.46.0 to match latest release#167
Merged
Conversation
The committed [package] version had been stuck at 0.41.0 while release tags advanced to v0.46.0. Release CI rewrites this from the tag at build time, so released binaries were correct, but local/dev `cargo build` binaries reported a stale `aware 0.41.0` (and stamped 0.41.0 as the lockfile compiler-version via env!(CARGO_PKG_VERSION)). Bump to 0.46.0 so dev builds match the current release line. Not bumping to 0.47 — that happens when the next release tag is cut.
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.
Summary
The committed
cli/Cargo.toml[package]version had been stuck at0.41.0while release tags advanced tov0.46.0. Release CI (therelease.yml"Sync crate version from tag" step) rewrites this from the tag at build time, so released binaries were always correct — but local/devcargo buildbinaries reported a staleaware 0.41.0, and stamped0.41.0as the lockfilecompiler-version(viaenv!("CARGO_PKG_VERSION")).Bump the committed version to
0.46.0so dev builds match the current release line. Not bumping to 0.47 — that happens when the next release tag is cut.Verification
cargo buildgreen;aware --versionnow reportsaware 0.46.0(was0.41.0).Notes
Both production version surfaces (
aware --versionvia clap, lockfilecompiler-version) derive fromCARGO_PKG_VERSION, so this one change fixes both. The0.42/0.43strings insidecar.rsand0.24.0inapp_lock.rsare test fixtures, not stale version references — intentionally left as-is.