Skip to content

chore: bump to 0.10.1 - #117

Merged
otsobide merged 1 commit into
developfrom
release/0.10.1
Aug 28, 2026
Merged

chore: bump to 0.10.1#117
otsobide merged 1 commit into
developfrom
release/0.10.1

Conversation

@otsobide

Copy link
Copy Markdown
Owner

Version bump only: eight strings and four lockfiles, nothing else in the diff —
the same twelve files every bump touches.

Why 0.10.1 and not 0.11.0

Nothing since v0.10.0 gains or loses a capability. The naming machinery removed
in #116 was already unreachable, and the CLI message that shipped alongside it
promised a replacement nobody could give while pointing at a desktop dialog
whose answers reached nothing.

One judgement call worth a second opinion: the desktop app visibly loses its
naming dialog. It never worked — it asked, took an answer and refused anyway —
so nothing that functioned was taken away, which is what makes this a patch. If
you would rather signal a visible UI change, this is the moment to say so; the
bump is cheap to redo.

Verified

  • Twelve locations agree on 0.10.1; no 0.10.0 remains in any manifest or lockfile of ours.
  • Lockfiles regenerated with cargo update --workspace and npm install --package-lock-only, not hand-edited.
  • cargo build --locked passes, which is the check make cli/release fails on first if a lockfile drifted.
  • make test green: 595 Rust, 88 Vitest.

The branch is named release/* so CI runs the macOS and Windows suites and the
cross-platform desktop builds on it.

All eight version strings and the four lockfiles. The release guard checks two
of them (issue #77), so the rest are by hand and by eye — though this time the
lockfiles were regenerated by `cargo update --workspace` and `npm install
--package-lock-only` rather than edited, since both toolchains are on this
machine now, and `cargo build --locked` was run afterwards because that is what
`make cli/release` uses and a drifted lockfile fails there first.

Patch rather than minor. Nothing since v0.10.0 gains or loses a capability: the
naming machinery that came out was already unreachable, and what shipped in its
place was a CLI refusal message that promised a replacement nobody could give
and pointed at a desktop dialog that collected answers reaching nothing. That
message now says what is true.

The one thing a user could notice is that the desktop's naming dialog is gone.
It never worked — it asked a question, took an answer and refused anyway — so
its removal takes away nothing that functioned, which is why this is a patch and
not a minor.
@otsobide
otsobide merged commit 1f57c0f into develop Aug 28, 2026
20 checks passed
@otsobide otsobide mentioned this pull request Aug 28, 2026
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant