release: cut v0.1.0 #224

Merged
natsukium merged 1 commit from chore/release-v0.1.0-31 into main 2026-09-08 03:33:18 +09:00
Owner

Refs #31.

The revision v0.1.0 will name. The tag is not pushed by this PR; it goes on the merged main commit once this lands green.

  • CHANGELOG.md: the accrued entries become ## [0.1.0] - 2026-09-08, a fresh empty ## [Unreleased] opens above them, the pre-release sentence ("until a first release is tagged…") states the released rule, and the Keep a Changelog link footers are added. scripts/release/verify.sh requires the dated section for a final tag, and release.yml lifts the release body out of it.
  • The CLI epoch's rename rule was conditional on this tag (skills/felis/SKILL.md, docs/explanation/architecture/control-surfaces.md). Both now state the rule that binds, which is what docs/reference/cli.md "Machine output" already said unconditionally.

Deliberately unchanged: the proto surface's pre-release framing (docs/reference/ipc.md, docs/reference/workspace.md "Versioning", crates/felis-protocol/proto/BREAKING.md). The committed first-release acknowledgment is the compatibility base this tag is checked against; it is retired in the first commit after the tag, and the wording goes with it.

Release-readiness checks run against this commit:

  • every #12 P0/P1 child plus #42/#53/#54 is closed; the only open issues left in the repo are P2.
  • just schema and just proto produce no diff.
  • just check, just prose-check, and just release-check v0.1.0 (with a throwaway local annotated tag, deleted again) all pass.
Refs #31. The revision `v0.1.0` will name. The tag is **not** pushed by this PR; it goes on the merged `main` commit once this lands green. - `CHANGELOG.md`: the accrued entries become `## [0.1.0] - 2026-09-08`, a fresh empty `## [Unreleased]` opens above them, the pre-release sentence ("until a first release is tagged…") states the released rule, and the Keep a Changelog link footers are added. `scripts/release/verify.sh` requires the dated section for a final tag, and `release.yml` lifts the release body out of it. - The CLI epoch's rename rule was conditional on this tag (`skills/felis/SKILL.md`, `docs/explanation/architecture/control-surfaces.md`). Both now state the rule that binds, which is what `docs/reference/cli.md` "Machine output" already said unconditionally. Deliberately unchanged: the proto surface's pre-release framing (`docs/reference/ipc.md`, `docs/reference/workspace.md` "Versioning", `crates/felis-protocol/proto/BREAKING.md`). The committed `first-release` acknowledgment is the compatibility base this tag is checked against; it is retired in the first commit after the tag, and the wording goes with it. Release-readiness checks run against this commit: - every #12 P0/P1 child plus #42/#53/#54 is closed; the only open issues left in the repo are P2. - `just schema` and `just proto` produce no diff. - `just check`, `just prose-check`, and `just release-check v0.1.0` (with a throwaway local annotated tag, deleted again) all pass.
release: cut v0.1.0
All checks were successful
darwin / detect relevant changes (pull_request) Successful in 3s
darwin / build felis (aarch64-darwin) (pull_request) Has been skipped
pr / nix flake check (pull_request) Successful in 20s
pr / cargo build / clippy / test / deny (pull_request) Successful in 1m45s
pr / wire schema is compatible with the base (pull_request) Successful in 10s
pr / frontend smoke (x86_64-linux) (pull_request) Successful in 52s
pr / publish felis (x86_64-linux) (pull_request) Has been skipped
windows / detect relevant changes (pull_request) Successful in 3s
windows / cargo clippy (Windows cross) (pull_request) Has been skipped
windows / cargo nextest (Windows) (pull_request) Has been skipped
windows / frontend smoke (Windows) (pull_request) Has been skipped
windows / package felis (x86_64-pc-windows-msvc) (pull_request) Has been skipped
darwin / darwin docs-only no-op (pull_request) Successful in 0s
windows / windows docs-only no-op (pull_request) Successful in 0s
darwin / detect relevant changes (push) Successful in 3s
darwin / build felis (aarch64-darwin) (push) Has been skipped
pr / nix flake check (push) Successful in 6s
pr / cargo build / clippy / test / deny (push) Successful in 1m51s
pr / wire schema is compatible with the base (push) Successful in 8s
pr / frontend smoke (x86_64-linux) (push) Successful in 5s
darwin / darwin docs-only no-op (push) Successful in 0s
pr / publish felis (x86_64-linux) (push) Successful in 11s
windows / detect relevant changes (push) Successful in 3s
windows / cargo clippy (Windows cross) (push) Has been skipped
windows / cargo nextest (Windows) (push) Has been skipped
windows / frontend smoke (Windows) (push) Has been skipped
windows / package felis (x86_64-pc-windows-msvc) (push) Has been skipped
windows / windows docs-only no-op (push) Successful in 0s
83b959e57a
This is the revision `v0.1.0` names, so the surfaces that describe felis
as untagged have to describe the release instead.

`CHANGELOG.md` dates the accrued entries as `[0.1.0]` and opens an empty
`[Unreleased]` above them; `scripts/release/verify.sh` requires the dated
section for a final tag, and `release.yml` lifts the release body out of
it. The Keep a Changelog link footers give both headings the compare and
tag URLs a reader follows.

The CLI machine contract's epoch rule was written conditionally, waiting
for this tag: a rename could ride the CHANGELOG under the same `"v"`
until a release shipped. It has shipped, so `skills/felis/SKILL.md` and
the control-surfaces rationale now state the rule that binds -- fields
added within the epoch, no rename or retype without bumping `v` -- which
is what `docs/reference/cli.md` "Machine output" already stated.

The proto surface keeps its pre-release framing here on purpose: the
`first-release` acknowledgment in `crates/felis-protocol/proto/BREAKING.md`
is the compatibility base this tag is checked against, and it is retired
in the first commit after the tag.

Refs #31
natsukium deleted branch chore/release-v0.1.0-31 2026-09-08 03:33:18 +09:00
Sign in to join this conversation.
No description provided.