release: v0.3.0 — FIX text protocol adapter (#29), perf flamegraph (#32), anchor sweep#132
release: v0.3.0 — FIX text protocol adapter (#29), perf flamegraph (#32), anchor sweep#132div0rce wants to merge 1 commit into
Conversation
…sweep Bump the project version 0.2.0 -> 0.3.0 and record the release. - CMakeLists.txt: project VERSION 0.3.0. - CHANGELOG.md: new [0.3.0] section — FIX-like text protocol adapter (#29), `make flamegraph` + dependency-free renderer (#32), and the Codex resume-anchor / PMU-claim consistency sweep (#127/#128 follow-up); [Unreleased] reset. - PROGRESS.md / HANDOFF.md: release and resume anchors brought to the v0.3.0 released state; #29 and #32 marked done. No code or benchmark artifacts change in this release PR. On squash-merge, tag `v0.3.0` on the merge commit and publish the GitHub release. make check 261/261. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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 |
![codescene-delta-analysis[bot]](https://avatars.githubusercontent.com/in/53921?s=60&v=4){kind=small}
There was a problem hiding this comment.
No application code in the PR — skipped Code Health checks.
See analysis details in CodeScene
Quality Gate Profile: Pay Down Tech Debt
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.
|
Superseded by the v0.2.1 release PR (maintainer chose a patch bump instead of minor). |
![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
Line 47 in 4331bac
Remove completed issues from resume backlog
When the next session follows PROGRESS.md as the repo's single source of truth, this line still lists #32 and #29 as remaining backlog even though the new v0.3.0 state above says they shipped via PR #130/#131. That stale resume anchor can send automation or humans to reopen already-closed work instead of focusing only on #94 and #90; update/remove these references, including the nearby blocker text, so the post-release state is actionable.
ℹ️ 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".
| - Synced the `/resume` anchors and perf-evidence wording to the released `v0.2.0` state and narrowed | ||
| an overstated Apple **Blizzard** (E-core) PMU claim — those rows read `<not counted>` because the | ||
| single-threaded benchmark stays on the Avalanche P-cores (Codex follow-up to PRs #127/#128): | ||
| `PROGRESS.md`, `AGENTS.md`/`CLAUDE.md` agreement, and `docs/perf_analysis.md`. |
There was a problem hiding this comment.
This entry says the release sweep includes AGENTS.md/CLAUDE.md agreement, but in this commit both files still end at the v0.2.0 state and omit the v0.3.0 PR stack entirely. Since /resume tells agents to read AGENTS/CLAUDE before PROGRESS/HANDOFF, a fresh session can reconstruct the old release state even after this bump; update those two memory files alongside the v0.3.0 anchors.
Useful? React with 👍 / 👎.
| - **Last completed docs sync:** v0.3.0 release prep (this PR): version bump + CHANGELOG `[0.3.0]` | ||
| and resume/release anchors brought current |
There was a problem hiding this comment.
This marks the v0.3.0 release prep as current, but docs/release_readiness.md still says the audit covers v0.2.0, lists the old 241-test verification, and calls v0.2.0 the next GitHub release. A reviewer following the release evidence will therefore see stale readiness data instead of the 261-test v0.3.0 state recorded here; update the audit or avoid claiming the release anchors are current.
Useful? React with 👍 / 👎.
1 participant
Summary
Version bump
v0.2.0→v0.3.0, recording the two reprioritized backlog items plus the resume-anchor/PMU consistency sweep delivered in this stack.Changes
CMakeLists.txt: projectVERSION 0.3.0.CHANGELOG.md: new[0.3.0]section (FIX adapter FIX-like text protocol adapter #29,make flamegraphFollow-up: generate flamegraph profiling artifact #32, Codex resume-anchor/PMU sweep);[Unreleased]reset.PROGRESS.md/HANDOFF.md: release +/resumeanchors moved to thev0.3.0released state; FIX-like text protocol adapter #29 and Follow-up: generate flamegraph profiling artifact #32 marked done.No code or benchmark artifacts change in this PR — it is the version/record bump only.
make check261/261.Why 0.3.0 (minor)
Additive feature (FIX adapter) + new tooling (flamegraph) + docs; no breaking changes to existing APIs or wire formats. Same honesty bar — deterministic simulator, no production/latency/profitability claims.
🤖 Generated with Claude Code