feat: create a Forgejo Release in create-release, not just a tag #5

Merged
David merged 1 commit from feat/create-forgejo-release into main 2026-06-14 01:29:14 +02:00
Owner

Make just create-release create 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.

Make `just create-release` create 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.
feat: create a Forgejo Release in create-release, not just a tag
All checks were successful
Test / Install Nushell 0.100.0 (push) Successful in 3s
Test / Install Nushell 0.101.0 (push) Successful in 5s
Test / Install Nushell latest (pull_request) Successful in 4s
Test / Install Nushell latest (push) Successful in 5s
Test / Install Nushell 0.101.0 (pull_request) Successful in 5s
Test / Install Nushell 0.100.0 (pull_request) Successful in 5s
8fbfbdc6f7
Pushing a tag alone populates the repo's tags list but leaves the releases list empty. The sibling repos get a Release entry from their post-merge create-release workflow; this action has no such workflow, so the recipe now creates the Release itself.

After pushing the vX.Y.Z tag the recipe calls `fj release create` (the canonical CLI, run with --host dev.a8n.run since keys.json holds more than one host) to attach a Release to that tag, with a changelog built from the previous release tag to HEAD (all commits on the first release). The floating major tag still moves but gets no separate Release. The mirror carries the tag to GitHub, where publishing to the Marketplace remains a manual step.
David force-pushed feat/create-forgejo-release from 8fbfbdc6f7
All checks were successful
Test / Install Nushell 0.100.0 (push) Successful in 3s
Test / Install Nushell 0.101.0 (push) Successful in 5s
Test / Install Nushell latest (pull_request) Successful in 4s
Test / Install Nushell latest (push) Successful in 5s
Test / Install Nushell 0.101.0 (pull_request) Successful in 5s
Test / Install Nushell 0.100.0 (pull_request) Successful in 5s
to f57e79265f
All checks were successful
Test / Install Nushell 0.100.0 (pull_request) Successful in 7s
Test / Install Nushell 0.100.0 (push) Successful in 9s
Test / Install Nushell 0.101.0 (push) Successful in 10s
Test / Install Nushell latest (push) Successful in 11s
Test / Install Nushell latest (pull_request) Successful in 35s
Test / Install Nushell 0.101.0 (pull_request) Successful in 39s
2026-06-14 01:29:02 +02:00
Compare
David merged commit 77f74c8337 into main 2026-06-14 01:29:14 +02:00
David deleted branch feat/create-forgejo-release 2026-06-14 01:29:14 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pandoras-box/action-install-nushell!5
No description provided.