jqueuniet/dm2-tools

Fork 0

chore: prepare for v0.2.1 release #326

Merged

jqueuniet merged 1 commit from chore/release-0.2.1 into main

2026-09-05 08:28:59 +02:00

jqueuniet commented

2026-09-05 08:25:33 +02:00

Owner

Version bump and changelog cut for v0.2.1.

What changed

cargo set-version --workspace 0.2.1 — [workspace.package], the nine
inter-crate version requirements, and Cargo.lock.
bindings/python/pyproject.toml bumped by hand: it sits outside the cargo
workspace, so set-version does not reach it. This is the skew that shipped
in 0.2.0 and is now guarded — test_version_matches_workspace compares the
loaded cdylib's version against both [workspace.package] and
pyproject.toml.
The npm package needs no edit at all: wasm-pack reads the version straight
out of Cargo.toml.
CHANGELOG.md: [Unreleased] becomes [0.2.1] - 2026-09-05, a fresh empty
[Unreleased] opens above it, and the link references gain a [0.2.1] tag
entry with the compare link rebased onto v0.2.1.

The changelog's section order was Fixed, Added, Changed — an artifact of the
order entries were appended. Regrouped to the Added, Changed, Fixed that every
earlier release in the file uses. All 11 entries are intact and unaltered.

Verification

cargo check --workspace --locked passes, so the lockfile is in sync. The
Python suite passes against a rebuilt cdylib (7 passed), which is the real
check on the bump: it fails loudly if pyproject.toml and the workspace
disagree. No stale 0.2.0 remains in any manifest.

After merging

Tagging v0.2.1 fires the release workflow, which will exercise publish for
the first time — the one job never executed, though its release-API code is
unchanged from what shipped v0.2.0. Then, manually: cargo publish --workspace
(dry-run clean as of this branch's base), npm publish crates/dm2-wasm/pkg,
and the first PyPI upload if you want it.

Worth a read before tagging: publish lifts the 0.2.1 section verbatim into
the release body, and those entries were written incrementally as work landed
rather than as release notes for a reader.

Version bump and changelog cut for v0.2.1. ## What changed - `cargo set-version --workspace 0.2.1` — `[workspace.package]`, the nine inter-crate version requirements, and `Cargo.lock`. - `bindings/python/pyproject.toml` bumped by hand: it sits outside the cargo workspace, so `set-version` does not reach it. This is the skew that shipped in 0.2.0 and is now guarded — `test_version_matches_workspace` compares the loaded cdylib's version against both `[workspace.package]` and `pyproject.toml`. - The npm package needs no edit at all: wasm-pack reads the version straight out of `Cargo.toml`. - `CHANGELOG.md`: `[Unreleased]` becomes `[0.2.1] - 2026-09-05`, a fresh empty `[Unreleased]` opens above it, and the link references gain a `[0.2.1]` tag entry with the compare link rebased onto `v0.2.1`. The changelog's section order was Fixed, Added, Changed — an artifact of the order entries were appended. Regrouped to the Added, Changed, Fixed that every earlier release in the file uses. All 11 entries are intact and unaltered. ## Verification `cargo check --workspace --locked` passes, so the lockfile is in sync. The Python suite passes against a rebuilt cdylib (7 passed), which is the real check on the bump: it fails loudly if `pyproject.toml` and the workspace disagree. No stale `0.2.0` remains in any manifest. ## After merging Tagging `v0.2.1` fires the release workflow, which will exercise `publish` for the first time — the one job never executed, though its release-API code is unchanged from what shipped v0.2.0. Then, manually: `cargo publish --workspace` (dry-run clean as of this branch's base), `npm publish crates/dm2-wasm/pkg`, and the first PyPI upload if you want it. Worth a read before tagging: `publish` lifts the 0.2.1 section verbatim into the release body, and those entries were written incrementally as work landed rather than as release notes for a reader.

jqueuniet added 1 commit

2026-09-05 08:25:33 +02:00

chore: prepare for v0.2.1 release

CI / stable (pull_request) Successful in 1m36s

Details

CI / python bindings (3.11) (pull_request) Successful in 38s

Details

CI / msrv (1.90) (pull_request) Successful in 42s

Details

CI / audit (pull_request) Successful in 23s

Details

CI / msrv (1.90) (push) Successful in 43s

Details

CI / audit (push) Successful in 24s

Details

CI / stable (push) Successful in 1m37s

Details

CI / python bindings (3.11) (push) Successful in 39s

Details

Release / wheel + c bundle (manylinux x86_64) (push) Successful in 1m44s

Details

Release / build (cli + windows wheel + c bundle) (push) Successful in 2m14s

Details

Release / publish (push) Successful in 23s

Details

9ed7aebfbb

`cargo set-version --workspace 0.2.1` covers `[workspace.package]` and the
nine inter-crate requirements; `bindings/python/pyproject.toml` sits outside
the cargo workspace and is bumped by hand, as the release docs describe. The
npm package needs no edit — wasm-pack reads the version out of Cargo.toml.

The changelog's accumulated section order (Fixed, Added, Changed) is
regrouped to the Added, Changed, Fixed that every earlier release in the file
uses. No entries were altered.

jqueuniet merged commit 9ed7aebfbb into main

2026-09-05 08:28:59 +02:00

jqueuniet deleted branch chore/release-0.2.1

2026-09-05 08:28:59 +02:00

No reviewers

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

jqueuniet/dm2-tools!326

No description provided.

Rows
Columns