release-process: mark v0.10 alpha as published - #80
Conversation
Record durable post-publication evidence for v0.10.0-alpha.1 without changing the immutable release tag: - policy.toml v0_10 boundary: status publish_ready -> published, plus tag, workflow-run, milestone-closure, and no-crates evidence; the release_policy_tracks_v0_10_boundary regression now asserts the published fields. - docs/releases/v0.10.0-alpha.1.md: published status, publication evidence, and Publication Evidence section. - ROADMAP, README, release-process README, and test-plan: mark the release published with release URL, tag, run IDs, and milestone closure. - CHANGELOG: note the publish-marking under [Unreleased]. Release: https://github.com/flyingrobots/edict/releases/tag/v0.10.0-alpha.1
|
Warning Review limit reached
More reviews will be available in 53 minutes and 52 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughRecords post-publication evidence for Changesv0.10.0-alpha.1 Publication Evidence Recording
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~4 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/topics/release-process/test-plan.md`:
- Line 69: Add the missing v0.10 requirement and test-case rows to the topic
test plan so it covers the v0.10.0-alpha.1 release boundary and the executable
evidence release_policy_tracks_v0_10_boundary. Update the relevant entries in
test-plan.md with new RELEASE-REQ-* and RELEASE-TP-* rows, linking the fixture,
oracle, and implemented evidence so the owning shelf matches the test added in
this PR.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: c5cfce96-2f75-43bc-8d46-201b96534083
📒 Files selected for processing (8)
CHANGELOG.mdREADME.mdROADMAP.mddocs/releases/v0.10.0-alpha.1.mddocs/topics/release-process/README.mddocs/topics/release-process/policy.tomldocs/topics/release-process/test-plan.mdxtask/src/main.rs
📜 Review details
🧰 Additional context used
📓 Path-based instructions (3)
**
⚙️ CodeRabbit configuration file
**: # AGENTSGit Rules
NEVER amend git commits. Make a new commit instead.
NEVER use
git rebaseunless the user explicitly approves a rare exception.
Use regular merge commits.NEVER force any git operation. If a force operation appears necessary, stop and
explain what happened and what options remain.NEVER create draft pull requests.
NEVER use a
codexprefix in branch names, PR titles, or commit messages.Pull request bodies for issue work MUST include GitHub auto-close text such as
Closes#123`` for every issue the PR is intended to close.Think
Think is durable memory for cross-session coordination.
- Use
codex-think --remember --jsonwhen starting a new session, changing into
this repository, or regaining context after a context shift.- Use
codex-think "..." --jsonwhen a cycle closes or a significant event
should survive across turns.- Treat Think as memory, not repo truth. Anchor strong claims back to files,
commits, commands, issues, or pull requests.- Claude memories are read-only. Use
claude-think --remember --jsononly for
additional context.Topic Shelves
docs/topics/contains the living contract graph for landed behavior. Topic
shelves are not proposals, retrospectives, or design archaeology.Each shelf may contain:
README.md: what is true in HEAD.test-plan.md: how those truths are verified, including requirements, cases,
fixtures, oracles, implemented evidence, planned cases, and known gaps.architecture.md: optional structure or dataflow notes when the machinery
earns a separate page.rationale.md: optional still-relevant tradeoffs and rejected approaches.When To Update Topic Shelves
For every nontrivial behavior, contract, workflow, release, schema, validation,
or public-surface change:
- Identify the owning topic shelf before editing code.
- If no shelf owns durable behavior, create one.
- Update
test-plan.mdbefore or alongside tests with requirement IDs, case
IDs,...
Files:
CHANGELOG.mddocs/topics/release-process/test-plan.mddocs/topics/release-process/policy.tomlREADME.mdROADMAP.mddocs/releases/v0.10.0-alpha.1.mddocs/topics/release-process/README.mdxtask/src/main.rs
docs/topics/**/test-plan.md
📄 CodeRabbit inference engine (AGENTS.md)
docs/topics/**/test-plan.md: Update a topic shelftest-plan.mdbefore or alongside tests with requirement IDs, case IDs, fixtures, oracles, implemented evidence, planned cases, and known gaps.
Mark planned cases as implemented only when executable evidence exists.
Do not usepolicyrows in topic-shelf test plans to avoid writing behavior tests for software behavior.
Negative tests in topic-shelf test plans should assert stable error kinds or structured artifacts, not merelyis_err()or diagnostic text.
For nontrivial behavior, contract, workflow, release, schema, validation, or public-surface changes, update the owning topictest-plan.mdwith planned requirement and case rows before or alongside the first test.
Mark planned rows as implemented only after executable evidence exists.
Files:
docs/topics/release-process/test-plan.md
docs/topics/**/README.md
📄 CodeRabbit inference engine (AGENTS.md)
docs/topics/**/README.md: Topic shelfREADME.mdfiles must describe only what is true in HEAD.
Update the topic shelfREADME.mdonly after the behavior exists in the branch; do not describe intended future behavior there.
Do not churn topic-shelf README files for purely mechanical edits that do not change a contract.
Files:
docs/topics/release-process/README.md
🔇 Additional comments (8)
ROADMAP.md (1)
399-408: LGTM!README.md (2)
523-529: LGTM!
575-580: LGTM!CHANGELOG.md (1)
11-16: LGTM!docs/topics/release-process/policy.toml (1)
400-414: LGTM!xtask/src/main.rs (1)
2736-2750: LGTM!docs/releases/v0.10.0-alpha.1.md (1)
5-6: LGTM!Also applies to: 17-24, 91-127
docs/topics/release-process/README.md (1)
75-75: LGTM!Also applies to: 97-111
Address CodeRabbit: the v0.10 release notes fixture had no matching RELEASE-REQ / RELEASE-TP coverage. Add RELEASE-REQ-022 and the RELEASE-TP-017 boundary guard citing release_policy_tracks_v0_10_boundary, mirroring the RELEASE-REQ-021 / RELEASE-TP-016 pair for v0.9.
|
Resolved in e79e4f1. Added @coderabbitai good catch — that pair belonged in the release-prep PR. |
|
Tip For best results, initiate chat on the files or code changes.
ᕱᕱ ✨ If you found this review helpful, would you consider giving us a shout-out on X? Thank you for using CodeRabbit! |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d2fbede8fe
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Status: published | ||
|
|
||
| Milestone: `v0.10.0-alpha.1` (#11) | ||
|
|
||
| Primary issues: #75, #76 (closed) | ||
|
|
||
| Release: <https://github.com/flyingrobots/edict/releases/tag/v0.10.0-alpha.1> |
There was a problem hiding this comment.
Marking the release as published here leaves the same roadmap internally inconsistent: the GitHub Artifact Map still lists v0.10.0-alpha.1 as planned, issues TBD instead of the milestone/issues now recorded in this section. Readers using the artifact map after this publication will get stale release tracking data, so update that entry in the same change.
Useful? React with 👍 / 👎.
| | docs/releases/v0.6.0-alpha.1.md | Published release notes for the developer-tooling alpha. | The release workflow looks up this file by full tag name. | | ||
| | docs/releases/v0.7.0-alpha.1.md | Published release notes for the file-backed authority-facts alpha. | The release workflow looked up this file by full tag name after the release-prep PR merged. | | ||
| | docs/releases/v0.8.0-alpha.1.md | Published release notes for the minimal effectful compiler-spine alpha. | The release workflow looked up this file by full tag name after the release-prep PR merged. | | ||
| | docs/releases/v0.10.0-alpha.1.md | Published release notes for the first public CLI alpha. | The release workflow looked up this file by full tag name after the release-prep PR merged. | |
There was a problem hiding this comment.
This only adds the v0.10 release notes as a fixture, but the release-process test plan still has no RELEASE-REQ-* or RELEASE-TP-* row for the release_policy_tracks_v0_10_boundary evidence added in xtask. That violates the repo-level AGENTS.md instruction for release/contract changes to update test-plan.md with requirement IDs and case IDs, and leaves the durable test plan unable to explain which requirement the v0.10 publication metadata test covers.
Useful? React with 👍 / 👎.
| milestone_closed_at = "2026-06-29T04:21:11Z" | ||
| milestone_open_issues = 0 |
There was a problem hiding this comment.
As of this review, the public milestone #11 page still shows v0.10.0-alpha.1 as Open with 2 open issues (#76 and #79), so these structured fields lock false release evidence into release_policy_tracks_v0_10_boundary. Please either update the recorded evidence to match the actual GitHub state or close the milestone/issues before asserting milestone_closed_at and milestone_open_issues = 0.
Useful? React with 👍 / 👎.
|
|
||
| Milestone: `v0.10.0-alpha.1` (#11) | ||
|
|
||
| Primary issues: #75, #76 (closed) |
There was a problem hiding this comment.
The public issue page for #76 still reports the release issue as Open, so adding (closed) for both primary issues makes the roadmap's v0.10 status inaccurate even though #75 is closed. Update this parenthetical to distinguish the open release issue, or close #76 before landing the publication evidence.
Useful? React with 👍 / 👎.
1 participant
Post-publication hygiene for
v0.10.0-alpha.1(mirrors #72 for v0.9). Records durable evidence onmainwithout touching the immutable tag.v0.10.0-alpha.1is published as a GitHub prerelease:2026-06-29T04:21:11Z, prerelease, 0 assets, no crates.11e516c8…; peeled commit6228341….28348355987, Auto Release Tag28348383070, Release28348397035.Changes
policy.tomlv0_10 boundarypublish_ready → published+ evidence;release_policy_tracks_v0_10_boundarynow asserts the published fields.docs/releases/v0.10.0-alpha.1.md: published status, publication evidence, Publication Evidence section.[Unreleased].cargo test -p xtask release_policy_tracks_v0_10_boundary✅ ·cargo xtask verify✅ · markdownlint ✅.