release: prepare v0.7.0 - #36
Merged
Merged
Conversation
- bump root version metadata 0.6.0 -> 0.7.0 - add release notes naming six behavioral changes: untargeted multi-pending first-payload batch eligibility, current-only ReferenceCatalog inventory output bytes (plus the trailing-newline residual), stricter fail-closed inventory conflict detection, hasResourcePage cardinality, narrower Turtle IRI compaction, and nested-source acceptance - minor rather than patch: d6f87ca makes a previously-refused untargeted invocation succeed ("supports exactly one weave candidate; found 2"), which is a capability change, not a fix - record that v0.7.0 is the first release able to generate the published SFLO mesh; v0.6.0 provably cannot, and no regeneration is needed because src/, scripts/, and deno.json are unchanged since the publication pin 2f04b71 and no generated artifact embeds a version - verify source quality gate: deno task ci green, 780 passed, 0 failed - maintenance log: gh-pages worktree resync resolved, and the "current code" terminology gap recorded Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe project version changed to 0.7.0. Release notes document four behavioral changes, validation results, limitations, artifacts, and follow-up work. The maintenance log records publication synchronization and release preparation details. Changesv0.7.0 release preparation
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 `@documentation/notes/wd.maintenance.2026-08.md`:
- Line 44: Correct the v0.7.0 release-prep entry by replacing the claim that the
combined `src/`, `scripts/`, and `deno.json` diff is empty with evidence that
only the source directories are unchanged, while explicitly noting the expected
`deno.json` version bump from 0.6.0 to 0.7.0; do not use that combined range as
evidence that the published corpus needs no regeneration.
🪄 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: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: bb14ae1a-f3db-49df-b970-b8ace3fb894e
📒 Files selected for processing (3)
deno.jsondocumentation/notes/release-notes.v0.7.0.mddocumentation/notes/wd.maintenance.2026-08.md
| - 2026-08-01 — note for Dave: the local publication worktree `/home/djradon/sites/sflo-gh-pages` still sits at the old tip `a7e7626` (clean, no uncommitted work). After the force-push it reads "ahead 2, behind 1"; resync with `git -C /home/djradon/sites/sflo-gh-pages fetch origin && git -C /home/djradon/sites/sflo-gh-pages reset --hard origin/gh-pages` | ||
| - 2026-08-02 — RESOLVED: the worktree above is resynced (HEAD and `gh-pages` both at `46b87d7`, tracking `origin/gh-pages`, clean, no divergence). Nothing outstanding | ||
| - 2026-08-02 — TERMINOLOGY GAP, worth not repeating: Dave read "regenerate with **current code**" in the SFLO publication ruling as meaning *the current release* (v0.6.0); it meant *the current commit on `main`*, pinned explicitly as `WEAVE_COMMIT` in the recipe and moved forward mid-task to `2f04b71` when the rehearsal surfaced the namespace-collision defect (PR #35). The publication therefore shipped on unreleased code by design, not by oversight — and could not have shipped on v0.6.0, which provably cannot generate that corpus. Lesson: when a ruling says "current code", pin and name the commit **and** state whether a release is expected to follow; "current" is ambiguous between the two seats | ||
| - 2026-08-02 — v0.7.0 release prep on `lane/release-v0.7.0`: version bumped 0.6.0 → 0.7.0, release notes written naming six behavioral changes (batch eligibility, inventory output bytes + trailing-newline residual, stricter fail-closed conflict detection, `hasResourcePage` cardinality, narrower IRI compaction, nested-source acceptance). Minor rather than patch because `d6f87ca` makes a previously-refused untargeted invocation succeed. Established in prep: the published SFLO corpus needs NO regeneration — `git diff 2f04b71..HEAD -- src/ scripts/ deno.json` is empty and no generated artifact embeds a Weave version, so v0.7.0 names the generator that already built it |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Version at 2f04b71:"
git show 2f04b71:deno.json | rg '"version"'
echo "Version at HEAD:"
rg '"version"' deno.json
echo "Diff:"
git diff 2f04b71..HEAD -- src/ scripts/ deno.jsonRepository: semantic-flow/weave
Length of output: 598
Correct the published-corpus evidence.
git diff 2f04b71..HEAD -- src/ scripts/ deno.json is not empty because deno.json changes from 0.6.0 to 0.7.0. Record the source-only empty diff plus the expected version metadata bump; do not use this range to claim the published corpus needs no regeneration.
🤖 Prompt for 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.
In `@documentation/notes/wd.maintenance.2026-08.md` at line 44, Correct the v0.7.0
release-prep entry by replacing the claim that the combined `src/`, `scripts/`,
and `deno.json` diff is empty with evidence that only the source directories are
unchanged, while explicitly noting the expected `deno.json` version bump from
0.6.0 to 0.7.0; do not use that combined range as evidence that the published
corpus needs no regeneration.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
The extracted-candidate batching follow-up moved out of the extractor defect-pair note (closed 2026-08-02, its own scope delivered) into wa.task.2026.2026-08-02_1330-extracted-term-weave-batch-path. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release preparation for
v0.7.0. No source changes — version bump, release notes, and maintenance log only.Scope
Four user-facing changes have accumulated on
mainsincev0.6.0(2026-07-31):fix: allow nested extraction sources without root Knopsfeat: batch untargeted multi-pending first-payload weavefix: append-only current-only ReferenceCatalog inventory weavefix: do not compact mesh IRIs into invalidsflo:prefixed namesWhy minor, not patch
Three of the four are
fix-labeled, but #33 makes a previously-refused invocation succeed — untargeted weave over a multi-pending first-payload mesh used to fail withsupports exactly one weave candidate; found 2. A consumer moving0.6.0 → 0.6.1is entitled to assume behavior only got more correct, not more capable, so one minor-shaped change makes the batch minor.Behavioral changes named
Per the runbook's v0.4.0 lesson, the notes name every behavioral change, not just the breaking ones — including two that can surface as new failures on an existing mesh:
SFLO publication
v0.7.0is the first release able to generate the published SFLO mesh (gh-pagesroot46b87d7), which was built frommainat2f04b71.v0.6.0provably cannot — the #35 defect made every weave of that mesh fail.No regeneration is needed.
git diff 2f04b71..HEAD -- src/ scripts/ deno.jsonis empty, and no generated artifact embeds a Weave version (page footers carry a frozen--generated-attimestamp and a bare repo link). This release names the generator that already built the corpus.Validation
deno task cigreen on this commit: 780 passed, 0 failed (~1m2s), lint/fmt/check clean.Merge GO and the
Release Manualworkflow run are yours.🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Documentation
Release