release: link the CHANGELOG to the Forgejo repository and gate it #448
No reviewers
Labels
No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
natsukium/felis!448
Loading…
Reference in a new issue
No description provided.
Delete branch "release/changelog-forgejo-links"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #393.
The CHANGELOG link references pointed at the GitHub mirror, which receives tags but no releases, so a release link could land on a bare tag with nothing to download. They now point at the public Forgejo repository,
https://git.natsukium.com/felis-terminal/felis, where the repository is about to be uploaded. Until then, the links return 404.tools/release/verify.pynow gates a final tag vX.Y.Z on two exact lines inCHANGELOG.md:[unreleased]: https://git.natsukium.com/felis-terminal/felis/compare/vX.Y.Z...HEAD[X.Y.Z]: https://git.natsukium.com/felis-terminal/felis/releases/tag/vX.Y.ZRelease candidates are exempt, as they already are for the dated section. The check matches whole lines and does not resolve link references the way Markdown does. Earlier drafts tried to match Markdown's resolution rules, and each draft ran into another edge case. A spelling that Markdown treats as equivalent, such as
[Unreleased]:, fails the gate on purpose.docs/reference/workspace.mditem 5 states the exact lines.Checks:
python3 tools/release/verify.py --self-testandjust checkpass. A sol review of the final form passed.Not needed: published links, including the CHANGELOG release links, stay on the GitHub mirror (github.com/felis-terminal/felis) for stability.