chore(release): target 0.2.0 (v0.1.0 tag burned by immutable bind)#45
Conversation
…ble bind)
v0.1.0 was bound to an immutable release, so GitHub forbids reusing that tag
("Tags previously bound to immutable releases can never be reused") even after
deletion. Skip to 0.2.0:
- release-as 0.1.0 -> 0.2.0
- manifest reset to 0.0.0 (clean first-release baseline; avoids a broken
v0.1.0...v0.2.0 compare link in the changelog)
- CHANGELOG.md back to a clean title (the prior file was re-mangled when a stale
0.1.0 release PR merged over the reset).
Signed-off-by: Sam Gammon <sam@elide.dev>
There was a problem hiding this comment.
Pull request overview
Updates Release Please configuration/state to skip v0.1.0 (tag burned by immutable release binding) and target a fresh v0.2.0, while resetting release metadata artifacts back to a clean baseline so the next Release Please PR is generated correctly.
Changes:
- Bumps
release-asfrom0.1.0to0.2.0inrelease-please-config.json. - Resets
.release-please-manifest.jsonto0.0.0for a clean “first-release” baseline. - Cleans
CHANGELOG.mdback to a single# Changelogheader.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| release-please-config.json | Targets 0.2.0 explicitly via release-as to avoid the burned v0.1.0 tag. |
| .release-please-manifest.json | Resets manifest version to 0.0.0 to re-baseline release-please state. |
| CHANGELOG.md | Removes the mangled prior content and restores a clean changelog header. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Merging this PR will not alter performance
|
Rather than resetting CHANGELOG.md to an empty title, preserve the hand-written changelog (the former [Unreleased] block) under the 0.2.0 heading. Drops only the boilerplate Keep-a-Changelog preamble (which release-please was mangling into a stray "## Changelog" section). Signed-off-by: Sam Gammon <sam@elide.dev>
v0.1.0was bound to an immutable release, so GitHub permanently burns that tag — "Tags previously bound to immutable releases can never be reused" — even after we deleted it. So we skip to 0.2.0.release-as:0.1.0→0.2.00.0.0(clean first-release baseline; avoids a brokenv0.1.0...v0.2.0compare link)CHANGELOG.md→ clean# Changelog(it had been re-mangled when a stale 0.1.0 release PR (chore(main): release 0.1.0 #43) merged over the earlier reset)Already cleaned up: the stuck
0.1.0release-please branch/PR (#44).After merge
release-please opens a fresh
release 0.2.0PR. Merging it runs the fixed flow: draft → assets + SBOM → attest → publish → BCR with entry attestation (immutable releases are now off). Tagv0.2.0is fresh/unused.Please merge this and then the 0.2.0 release PR back-to-back — don't leave other release PRs open simultaneously (overlapping PRs are what clobbered the last reset). After 0.2.0 ships, remove the
release-asline.