feat: create a Forgejo Release in create-release, not just a tag #5
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/create-forgejo-release"
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?
Make
just create-releasecreate a Forgejo Release, not only a tag.A pushed tag shows up under the repo's "tags" but the "releases" list stays empty (currently 2 tags, 0 releases). The sibling repos get their Release entry from a post-merge create-release.yml workflow that calls the Forgejo API. This action has no manifest to bump and no build pipeline, so it has no such workflow; the recipe creates the Release directly instead.
After pushing the immutable vX.Y.Z tag, the recipe now calls fj release create to attach a Release to that tag. fj is the canonical CLI (no raw API call), run with --host dev.a8n.run because keys.json holds more than one host. The release body is a changelog generated from the previous release tag to HEAD, or all commits on the first release. The floating major tag still moves to the release but gets no separate Release entry. The Forgejo tag mirrors to GitHub; publishing to the GitHub Marketplace remains a manual step there.
Validated: just --list parses and nu-check passes on the extracted recipe body.
8fbfbdc6f7f57e79265f