Repository navigation
chore: add an update_version task and bump the version to 1.8.1 - #226
Merged
Merged
Conversation
The version is set in five files (the three Cargo.toml files, r-phylo2vec/DESCRIPTION and pixi.toml), plus Cargo.lock, but update_version.py only handled py-phylo2vec/Cargo.toml and DESCRIPTION. Releases still got the right version because CD overwrites it from the tag, so the repo drifted (it still says 1.7.0 after v1.8.0). - update_version.py: add `--all --version X.Y.Z`, which sets the version in all five files and runs `cargo update --workspace --offline`. The existing options used by CD are unchanged - pixi.toml: add an `update_version` task, e.g. `pixi run update_version 1.9.0` - docs/development.md: add a "Releasing" section Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Set with `pixi run update_version 1.8.1`. The repo still said 1.7.0 after the v1.8.0 release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
Adds a
pixi run update_version <version>task to set the version of all packages before a release, and uses it to bump the version to 1.8.1.Why
The version is set in five files (
phylo2vec/Cargo.toml,py-phylo2vec/Cargo.toml,r-phylo2vec/src/rust/Cargo.toml,r-phylo2vec/DESCRIPTIONandpixi.toml), plusCargo.lock, and was bumped by hand (e.g., #175). Releases still get the right version because CD overwrites it from the release tag, so the repo can silently drift: it still says 1.7.0 after v1.8.0. This also means that installing from a tag (e.g.,devtools::install_github("sbhattlab/phylo2vec@v1.8.0", ...)) reports 1.7.0, and the development builds published to TestPyPI frommainare versioned1.7.1-rc.N.Changes
resources/update_version.py: new--all --version X.Y.Zoption, which sets the version in all five files (only theversionkey of[package]/[workspace], keeping the quote style) and runscargo update --workspace --offlineto updateCargo.lock. The existing options used by the CD workflows (--python,--r,--extract-only, automatic-rc.Nversions) are unchangedpixi.toml:update_versiontask, e.g.pixi run update_version 1.9.0docs/development.md: a "Releasing" section (run the task, merge, publish the release)Once merged, the
v1.8.1release can be published frommain.