release: cut v0.1.0 #224
No reviewers
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
natsukium/felis!224
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/release-v0.1.0-31"
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?
Refs #31.
The revision
v0.1.0will name. The tag is not pushed by this PR; it goes on the mergedmaincommit 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.shrequires the dated section for a final tag, andrelease.ymllifts the release body out of it.skills/felis/SKILL.md,docs/explanation/architecture/control-surfaces.md). Both now state the rule that binds, which is whatdocs/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 committedfirst-releaseacknowledgment 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:
just schemaandjust protoproduce no diff.just check,just prose-check, andjust release-check v0.1.0(with a throwaway local annotated tag, deleted again) all pass.