chore(release): v0.2.0#15
Conversation
First stable on the @mandarnilange/* scope. Bumps root, core, and platform package.json from 0.2.0-rc.2 to 0.2.0 and adds the [0.2.0] CHANGELOG entry covering P40 (config validation), P45 (distributed control plane T1-T6), and the skill-family + docs work landed since rc.2. P45-T7 (two-replica integration test) deferred to v0.2.1.
📝 WalkthroughWalkthroughThis PR cuts the stable 0.2.0 release. The CHANGELOG documents new capabilities (config validation, distributed control plane, skill family) and seven fixes from PR ChangesRelease 0.2.0
🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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: 2
🤖 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 `@CHANGELOG.md`:
- Line 6: There are two duplicate section headings "## [0.2.0]" in CHANGELOG.md;
locate both occurrences of the heading string "## [0.2.0]" and consolidate them
by either merging the entries under a single "## [0.2.0] — First stable: config
validation, distributed control plane, skill family" section or by renaming the
older/incorrect heading to its actual historical version, ensuring only one "##
[0.2.0]" remains and that related entries are preserved and de-duplicated for
release-note generation.
In `@packages/platform/package.json`:
- Line 3: Update the `@mandarnilange/agentforge-core` entries in
packages/platform/package.json: change both the "dependencies" and
"peerDependencies" versions from "^0.2.0-rc.2" to the stable "^0.2.0" so they
match the package's "version": "0.2.0" release; modify the dependency value for
the "@mandarnilange/agentforge-core" key in both sections (dependencies and
peerDependencies).
🪄 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: CHILL
Plan: Pro
Run ID: 65b3c64e-14fc-4fcb-8727-0f4b20a942b5
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (4)
CHANGELOG.mdpackage.jsonpackages/core/package.jsonpackages/platform/package.json
| All notable changes to this project are documented here. | ||
| Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). | ||
|
|
||
| ## [0.2.0] — First stable: config validation, distributed control plane, skill family |
There was a problem hiding this comment.
Duplicate 0.2.0 headings in changelog need consolidation.
Line 6 introduces a second ## [0.2.0] while another already exists at Line 149. This can make release-note generation ambiguous and mislead consumers about what belongs to the stable tag. Keep exactly one 0.2.0 section (or rename the older one to its correct historical version).
🤖 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 `@CHANGELOG.md` at line 6, There are two duplicate section headings "##
[0.2.0]" in CHANGELOG.md; locate both occurrences of the heading string "##
[0.2.0]" and consolidate them by either merging the entries under a single "##
[0.2.0] — First stable: config validation, distributed control plane, skill
family" section or by renaming the older/incorrect heading to its actual
historical version, ensuring only one "## [0.2.0]" remains and that related
entries are preserved and de-duplicated for release-note generation.
| { | ||
| "name": "@mandarnilange/agentforge", | ||
| "version": "0.2.0-rc.2", | ||
| "version": "0.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify version alignment for release metadata across package manifests.
fd -a package.json | while read -r f; do
jq -r --arg f "$f" '
[
$f,
.name,
.version,
(.dependencies["@mandarnilange/agentforge-core"] // "-"),
(.peerDependencies["@mandarnilange/agentforge-core"] // "-")
] | `@tsv`
' "$f"
doneRepository: mandarnilange/agentforge
Length of output: 412
Update @mandarnilange/agentforge-core dependency to stable version.
The platform package publishes as 0.2.0 (stable release), but dependencies and peerDependencies still pin @mandarnilange/agentforge-core to ^0.2.0-rc.2. Since @mandarnilange/agentforge-core is also released as 0.2.0 (stable), both constraints should be updated to ^0.2.0.
Proposed fix
"dependencies": {
- "@mandarnilange/agentforge-core": "^0.2.0-rc.2",
+ "@mandarnilange/agentforge-core": "^0.2.0",
"dockerode": "^4.0.10", "peerDependencies": {
- "@mandarnilange/agentforge-core": "^0.2.0-rc.2"
+ "@mandarnilange/agentforge-core": "^0.2.0"🤖 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 `@packages/platform/package.json` at line 3, Update the
`@mandarnilange/agentforge-core` entries in packages/platform/package.json: change
both the "dependencies" and "peerDependencies" versions from "^0.2.0-rc.2" to
the stable "^0.2.0" so they match the package's "version": "0.2.0" release;
modify the dependency value for the "@mandarnilange/agentforge-core" key in both
sections (dependencies and peerDependencies).
1 participant
Summary
package.jsonfrom0.2.0-rc.2to0.2.0(lockfile refreshed).## [0.2.0]CHANGELOG entry covering P40, P45 (T1–T6), and the skill-family/docs work since rc.2.Merging this PR and tagging
v0.2.0on the resulting commit triggers.github/workflows/release.yml→ npm publish (@mandarnilange/agentforge-core,@mandarnilange/agentforge) + GHCR images + GitHub Release with the CHANGELOG section as release notes.Test plan
npm run build(green)npx biome check .(green)npx vitest run— 154 files / 1659 tests passv0.2.0→ release workflow succeeds → both packages visible on npm at 0.2.0Deferred to v0.2.1
Summary by CodeRabbit
Release 0.2.0 - First Stable
New Features
Bug Fixes