Bump version to 0.4.6

[christophergeyer]

The v0.4.6 release build failed at its version guard:

Version mismatch: pyproject.toml=0.4.5 release_tag=v0.4.6

The tag was cut at e6a0831 (the merge of #297) while pyproject.toml still read 0.4.5. The guard worked — publishing 0.4.5's metadata under a 0.4.6 tag is the thing it exists to stop. What's missing is the bump commit; 0.4.5 had one (03b6dea chore(release): bump version to 0.4.5).

After merging

The existing v0.4.6 tag points at a commit without the bump, so it needs to move:

git tag -f v0.4.6 <new-main-sha> && git push -f origin v0.4.6

Then re-publish the GitHub Release — publish-pypi.yml triggers on release: published, not on the tag, so re-tagging alone won't rerun it. workflow_dispatch also works.

Notes

• The other failure on A version pin is not a credential #297's PR run — test_remote_label_edits_from_bare_directory, macOS-x86 only — was a 60s pytest timeout, not an assertion, and the same code passed on the push-to-main run. Flaky, unrelated to that change.
• uv.lock records roar-cli 0.4.4 for the editable self-reference. Already stale before 0.4.5 and it did not block that release, so it is left alone here rather than churning the lock inside a release fix.
• Worth considering separately: nothing enforces the bump before a tag is cut. A release script that bumps, commits and tags together would make this unrepeatable.