Skip to content

plan(v0.22): release-planning slices as requirements (release: v0.22.0)#602

Open
avrabe wants to merge 1 commit into
mainfrom
plan/v0.22-release-planning
Open

plan(v0.22): release-planning slices as requirements (release: v0.22.0)#602
avrabe wants to merge 1 commit into
mainfrom
plan/v0.22-release-planning

Conversation

@avrabe

@avrabe avrabe commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Makes the v0.22 plan live in the trace (not a spreadsheet) by filing the four scoped slices as proposed requirements, each tagged release: v0.22.0. Queryable today:

$ rivet list --filter '(= release "v0.22.0")'
REQ-232  rivet list --release <ver> filter sugar           (#516 §2)
REQ-233  rivet release status <ver> readiness burn-down    (#516 §3, centerpiece)
REQ-234  rivet release move <id> <ver> logged scope change (#516 §3)
REQ-235  rivet migrate --explode <source> to per-id files  (#490 §2, DD-070)

v0.22 theme: complete release-planning — finish what v0.21 started (the release: field is half-useful without a burn-down query). Each slice is small; the field + loader already exist.

Dogfood notes (both are wins of the methodology):

Once merged, v0.22 implementation starts at REQ-232 (list --release). validate PASS; docs check PASS.

Refs REQ-007, DD-070.

🤖 Generated with Claude Code

…0.22.0)

v0.22 theme: complete release-planning. Files the four scoped slices as proposed
requirements, each tagged release: v0.22.0 so the roadmap is live + queryable in
the trace itself (`rivet list --filter '(= release "v0.22.0")'`) rather than a
spreadsheet:

- REQ-232  rivet list --release <ver>            (#516 slice 2)
- REQ-233  rivet release status <ver> burn-down  (#516 slice 3, centerpiece)
- REQ-234  rivet release move <id> <ver>         (#516 slice 3)
- REQ-235  rivet migrate --explode <source>      (#490 slice 2, DD-070)

Dogfood note: filing these with --set-release exercised (and confirmed) the
v0.21.1 corruption fix — all four carry provenance blocks and validate cleanly.

Refs: REQ-007, DD-070
@github-actions

Copy link
Copy Markdown

📐 Rivet artifact delta

Change Count
Added 4
Removed 0
Modified 0
Downstream impacted (depth ≤ 5) 0

Graph

graph LR
  REQ_232["REQ-232"]:::added
  REQ_233["REQ-233"]:::added
  REQ_234["REQ-234"]:::added
  REQ_235["REQ-235"]:::added
  classDef added fill:#d4edda,stroke:#28a745,color:#155724
  classDef removed fill:#f8d7da,stroke:#dc3545,color:#721c24
  classDef modified fill:#fff3cd,stroke:#ffc107,color:#856404
  classDef overflow fill:#e2e3e5,stroke:#6c757d,color:#495057,stroke-dasharray: 3 3
Loading
Added
  • REQ-232
  • REQ-233
  • REQ-234
  • REQ-235

📎 Full HTML dashboard attached as workflow artifact rivet-delta-pr-602download from the workflow run.

Posted by rivet-delta workflow. The graph shows only changed artifacts; open the HTML dashboard (above) for full context.

@codecov

codecov Bot commented Jun 26, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant