fix: publish tag guard - v<version> must be among git tag --points-at (v0.12.1)
The first live run of daedalus publish on the v0.12.0 release was rejected by its own tag guard: git describe --exact-match returns whichever name git picks (here: latest), not the version tag, when several tags share the release commit. The guard now checks that v<version> is among git tag --points-at HEAD; moving tags on the same commit are fine (publish spec 3.3.2, reproduced by a new test). Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
This commit is contained in:
@@ -10,6 +10,18 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and
|
||||
|
||||
- Nothing yet.
|
||||
|
||||
## [0.12.1] - 2026-11-19
|
||||
|
||||
### Fixed in 0.12.1
|
||||
|
||||
- `publish`'s tag guard rejected a correctly tagged release when
|
||||
`latest` (or any other tag) shared the release commit: `git describe
|
||||
--tags --exact-match` returns whichever name git picks, not the
|
||||
version tag. The guard now checks that `v<version>` is among
|
||||
`git tag --points-at HEAD` (membership check, publish spec item
|
||||
3.3.2); moving tags on the same commit are fine. Found by the first
|
||||
live run of `daedalus publish` on the v0.12.0 release.
|
||||
|
||||
## [0.12.0] - 2026-11-19
|
||||
|
||||
### Added in 0.12.0
|
||||
|
||||
Reference in New Issue
Block a user