Conversation
- Bump version 0.5.0 → 0.6.0 - Update release notes with all 8 PRs (was missing #85, #86, #91, #94, #100, #106, #107) - Mark v0.6.0 as released in ROADMAP.md - Update FEATURES.md architecture section for hybrid event model - Expand "What's New in v0.6.0" with architectural simplification, bug fixes, tech debt - Fix README roadmap: v0.6.1 → v0.7.0 for loops - Update bug report template example version to 0.6.0
Contributor
Confidence Score: 5/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
subgraph "v0.6.0 Release Prep (this PR)"
A[version bump\n0.5.0 → 0.6.0] --> B[package.json +\npackage-lock.json]
C[docs update] --> D[RELEASE_NOTES_v0.6.0.md\nexpanded to cover all 8 PRs]
C --> E[ROADMAP.md\nv0.6.0 marked RELEASED]
C --> F[FEATURES.md\narchitecture section updated\nto hybrid event model]
C --> G[README.md\nroadmap fixed:\nv0.6.1 → v0.7.0]
C --> H[bug_report.md\nexample version 0.5.0 → 0.6.0]
end
subgraph "Actual v0.6.0 Features (merged PRs)"
I[#78 Scheduled Pipelines]
J[#85 runInTransaction]
K[#86 Multi-provider branding]
L[#91 Event system simplification\n42 → 25 events]
M[#94 SQLite worker coordination]
N[#100 ReadOnlyContext CLI]
O[#106 Bug fixes #84 #82 #95]
P[#107 Tech debt #101 #104 #83]
end
D --> I & J & K & L & M & N & O & P
Last reviewed commit: "docs: address PR rev..." |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
- README roadmap: expand v0.6.0 description to include architectural simplification - Release notes: fix cancelTasks description to say "all active executions" (not "current execution")
| | v0.4.0 | ✅ Released | Scheduling, Resumption, Rename to Backbeat | | ||
| | v0.5.0 | ✅ Released | Multi-Agent Support | | ||
| | v0.6.0 | 🎯 In Progress | Architectural Simplification + Bug Fixes | | ||
| | v0.6.0 | ✅ Released | Architectural Simplification + Bug Fixes | |
Contributor
There was a problem hiding this comment.
The version timeline table lists v0.6.0's focus as "Architectural Simplification + Bug Fixes", but the section heading directly above it (### v0.6.0 - Architectural Simplification + Bug Fixes ✅), the README, and the release notes all use "Architectural Simplification + Scheduled Pipelines" as the release's dual theme. Scheduled pipelines (PR #78) is the primary user-facing feature of the release and appears as the first listed feature in the v0.6.0 section — dropping it from the timeline summary could mislead readers scanning the version history.
Suggested change
| | v0.6.0 | ✅ Released | Architectural Simplification + Bug Fixes | | |
| | v0.6.0 | ✅ Released | Architectural Simplification + Scheduled Pipelines | |
The section heading on line 60 is the same issue:
### v0.6.0 - Architectural Simplification + Bug Fixes ✅
should read:
### v0.6.0 - Architectural Simplification + Scheduled Pipelines ✅
| - Node.js version: [e.g. 20.10.0] | ||
| - MCP client & agent CLI version: [e.g. claude latest, codex 0.1] | ||
| - Backbeat version: [e.g. 0.5.0] | ||
| - Backbeat version: [e.g. 0.6.0] |
Contributor
There was a problem hiding this comment.
The file still ends without a trailing newline (note the \ No newline at end of file marker in the diff). While this is a pre-existing condition, now that the file is being touched it's a good opportunity to fix the POSIX non-compliance.
Suggested change
| - Backbeat version: [e.g. 0.6.0] | |
| Add any other context about the problem here. |
(Add a blank line after the final sentence so the file ends with a newline.)
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.
Summary
0.5.0→0.6.0(package.json + package-lock.json)v0.6.1→v0.7.0for task/pipeline loops0.5.0→0.6.0GitHub Issues
Test plan
npm run build— clean compilationnpm run test:all— full suite passes (822 tests, 0 failures)npx biome check src/ tests/— no lint errorspackage.jsonversion is0.6.0