Describe the Bug
The build job compiles the release binaries while Cargo.toml still carries
version = "0.0.0-dev". The release and deb jobs reuse those artifacts, so the
published binaries and the deb report 0.0.0-dev from cubic --version. Only the
crate publish patches the version, and only the snap sets its own version, so the
version a user sees depends on how they installed cubic.
Where
.github/workflows/build.yml build job compiles without patching the version.github/workflows/build.yml publish-release reuses the build artifacts.github/workflows/build.yml package-deb builds from the unpatched manifest- publish-crate patches the version with sed and package-snap overrides it separately
Impact
A released binary and the deb both answer 0.0.0-dev to --version, which makes bug
reports harder and disagrees with the crate and snap versions.
Suggested Fix
Stamp the version once, early, before the build job compiles, derived from the tag, so
every artifact carries the same version. Then the release, deb, crate and snap agree.
Describe the Bug
The build job compiles the release binaries while
Cargo.tomlstill carriesversion = "0.0.0-dev". The release and deb jobs reuse those artifacts, so thepublished binaries and the deb report
0.0.0-devfromcubic --version. Only thecrate publish patches the version, and only the snap sets its own version, so the
version a user sees depends on how they installed cubic.
Where
.github/workflows/build.ymlbuild job compiles without patching the version.github/workflows/build.ymlpublish-release reuses the build artifacts.github/workflows/build.ymlpackage-deb builds from the unpatched manifestImpact
A released binary and the deb both answer
0.0.0-devto--version, which makes bugreports harder and disagrees with the crate and snap versions.
Suggested Fix
Stamp the version once, early, before the build job compiles, derived from the tag, so
every artifact carries the same version. Then the release, deb, crate and snap agree.