ci: republish each Forgejo release on the GitHub mirror #487

Merged

natsukium merged 2 commits from ci/github-release-mirror into main 2026-09-26 15:10:32 +09:00

Conversation 0 Commits 2 Files changed 9 +730 -7

natsukium commented 2026-09-26 13:49:30 +09:00

Owner

Copy link

Pre-v0.1.0 staleness sweep, plus the release mirror the sweep turned up as missing.

• docs: README linked benchmarks.md#summary, which does not exist (lychee offline does not check fragments); terminal-identity.md cited REQ-211 (NRCS) for the SCS no-op instead of REQ-213.
• ci: the GitHub push mirror carries refs but not release pages, so install.md had to send readers to Forgejo. .github/workflows/release-mirror.yml fires on the mirrored v* tag, waits for the Forgejo release to publish, and copies its body and assets to a GitHub release (draft first, published once every asset is attached). It uses only the workflow's own GITHUB_TOKEN and reads Forgejo anonymously. tools/release/mirror.py carries the logic; just release-mirror-test (now part of just selftest) runs it against a fake Forgejo and GitHub.

Before tagging v0.1.0: GitHub Actions must be enabled on felis-terminal/felis, and an rc.8 should exercise both this and the release-workflow changes merged since rc.7 (#477, #479).

Pre-v0.1.0 staleness sweep, plus the release mirror the sweep turned up as missing. - `docs:` README linked `benchmarks.md#summary`, which does not exist (lychee offline does not check fragments); `terminal-identity.md` cited REQ-211 (NRCS) for the SCS no-op instead of REQ-213. - `ci:` the GitHub push mirror carries refs but not release pages, so `install.md` had to send readers to Forgejo. `.github/workflows/release-mirror.yml` fires on the mirrored `v*` tag, waits for the Forgejo release to publish, and copies its body and assets to a GitHub release (draft first, published once every asset is attached). It uses only the workflow's own `GITHUB_TOKEN` and reads Forgejo anonymously. `tools/release/mirror.py` carries the logic; `just release-mirror-test` (now part of `just selftest`) runs it against a fake Forgejo and GitHub. Before tagging v0.1.0: GitHub Actions must be enabled on `felis-terminal/felis`, and an rc.8 should exercise both this and the release-workflow changes merged since rc.7 (#477, #479).

natsukium added 2 commits 2026-09-26 13:49:30 +09:00

docs: fix a dead benchmark anchor and a wrong REQ citation ... b8c63826e1

The README linked benchmarks.md#summary, but that page has no Summary
heading; lychee's offline mode does not check fragments, so the doc-links
gate let it through. terminal-identity.md cited REQ-211 (NRCS) for the SCS
no-op, which spec.md records as REQ-213.

Assisted-by: Claude Code

ci: republish each Forgejo release on the GitHub mirror ... c1a852227b

GitHub is the public face (issues, pull requests, the flake reference),
but the push mirror carries refs only, so a tag reached GitHub with no
release page and no assets, and install.md had to send readers to
Forgejo to download anything.

A GitHub workflow triggered by the mirrored tag waits for the Forgejo
release to publish, then copies its body and assets. It needs only the
workflow's own GITHUB_TOKEN and reads Forgejo anonymously, so neither
forge holds a credential for the other. Pushing to GitHub from
publish.py was the alternative; it would put a long-lived GitHub token
in Forgejo's secrets and fail the Forgejo release job on a GitHub
outage.

Assisted-by: Claude Code

natsukium merged commit 0057f3926d into main 2026-09-26 15:10:32 +09:00

natsukium deleted branch ci/github-release-mirror 2026-09-26 15:10:33 +09:00

natsukium referenced this pull request from a commit 2026-09-26 15:10:33 +09:00

ci: republish each Forgejo release on the GitHub mirror (#487)

natsukium referenced this pull request 2026-09-26 15:24:43 +09:00

ci: compare a tag's wire schema with the newest release's tag, not a committed copy #488

natsukium referenced this pull request from a commit 2026-09-26 15:41:30 +09:00

ci: compare a tag's wire schema with the newest release's tag, not a committed copy (#488)

Commenting is not possible because the repository is archived.

Reviewers

No reviewers

Labels

Clear labels   

priority/P0

Must be resolved before the v0.1.0 tag

  

priority/P1

Must be settled before the first public contract freezes

  

priority/P2

Explicitly deferred until after v0.1.0

  

release/v0.1.0

Work tracked for the first tagged release

  

status/blocked

Cannot start now: waits on an upstream release, another issue, or a recorded revisit trigger

  

status/planned

Triaged with a source-grounded plan and a passed pi review; ready to implement

  

type/bug

Shipped behavior that contradicts the docs or the code's own intent; needs a product code change

  

type/design

An open scope or trade-off question; needs a recorded decision in the owning explanation doc before code

  

type/test-gap

Documented or reviewed behavior that no test pins; usually split from a review finding, needs no product code change

  

type/tracker

Parent issue that tracks child work

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

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

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

natsukium/felis!487

No description provided.