natsukium/felis
Watch
1
Code Issues 27 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Complete the wire-gate release baseline workflow (Forgejo release API + baseline commit) #115

New issue
Open
opened 2026-09-05 00:20:06 +09:00 by natsukium · 1 comment
natsukium commented 2026-09-05 00:20:06 +09:00
Owner
Copy link

Migrated from docs/backlog.md (Blocked / Release baseline for the wire gate).

scripts/proto/compat.sh has a tag path (GITHUB_REF_TYPE=tag: compare with proto-baseline/, ignore BREAKING.md, accept first-release only while no baseline is committed), proven by its self-test, and release.yml's proto-compat job now takes it on every tag. That is the first of the three things the path was waiting for. Two remain, and both need the Forgejo release API rather than the repository: accept first-release only when the API reports no final release, and otherwise require proto-baseline/RELEASE to name the latest final release with a schema byte-equal to that release's attached felis.proto (a baseline behind the published release fails the tag, so a failed post-publish baseline commit blocks the next tag rather than narrowing the check); and commit the new baseline to main after a final release publishes (prerelease tags never update it). Until then first-release stays live indefinitely, which is the right answer only while no final release exists, and the baseline commit is a human step after the tag. The major the first post-release break lands on is a decision ipc.md "Versioning" leaves open until then.

Remaining work:

  1. Gate first-release on the Forgejo release API (accept only when no final release exists; otherwise require proto-baseline/RELEASE matches the latest final release's attached felis.proto byte-for-byte).
  2. Auto-commit the new baseline to main after a final release publishes (prerelease tags never update it).

Refs: docs/reference/ipc.md Versioning, docs/reference/testing.md Wire compatibility gates, scripts/proto/compat.sh, crates/felis-protocol/proto/BREAKING.md, .forgejo/workflows/release.yml.

Migrated from `docs/backlog.md` (Blocked / Release baseline for the wire gate). > `scripts/proto/compat.sh` has a tag path (`GITHUB_REF_TYPE=tag`: compare with `proto-baseline/`, ignore `BREAKING.md`, accept `first-release` only while no baseline is committed), proven by its self-test, and `release.yml`'s `proto-compat` job now takes it on every tag. That is the first of the three things the path was waiting for. Two remain, and both need the Forgejo release API rather than the repository: accept `first-release` only when the API reports no final release, and otherwise require `proto-baseline/RELEASE` to name the latest final release with a schema byte-equal to that release's attached `felis.proto` (a baseline behind the published release fails the tag, so a failed post-publish baseline commit blocks the next tag rather than narrowing the check); and commit the new baseline to `main` after a final release publishes (prerelease tags never update it). Until then `first-release` stays live indefinitely, which is the right answer only while no final release exists, and the baseline commit is a human step after the tag. The major the first post-release break lands on is a decision [ipc.md](reference/ipc.md) "Versioning" leaves open until then. Remaining work: 1. Gate `first-release` on the Forgejo release API (accept only when no final release exists; otherwise require `proto-baseline/RELEASE` matches the latest final release's attached `felis.proto` byte-for-byte). 2. Auto-commit the new baseline to `main` after a final release publishes (prerelease tags never update it). Refs: `docs/reference/ipc.md` Versioning, `docs/reference/testing.md` Wire compatibility gates, `scripts/proto/compat.sh`, `crates/felis-protocol/proto/BREAKING.md`, `.forgejo/workflows/release.yml`.
natsukium commented 2026-09-05 12:11:19 +09:00
Author
Owner
Copy link

Triage (2026-09-05)

P2, but time-bound. Not needed for the v0.1.0 tag itself (first-release is correct while no final release exists), but step 2 (commit proto-baseline/ after the release publishes) is the first thing due after #31, and step 1 must exist before the second tag. Listed on #12 as the post-release follow-up. #147 closed onto this issue.

## Triage (2026-09-05) **P2, but time-bound.** Not needed for the v0.1.0 tag itself (`first-release` is correct while no final release exists), but step 2 (commit `proto-baseline/` after the release publishes) is the first thing due after #31, and step 1 must exist before the second tag. Listed on #12 as the post-release follow-up. #147 closed onto this issue.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
ci/darwin-smoke
No results found.
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
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
natsukium/felis#115
No description provided.