[github-actions]

🤖 I have created a release beep boop

1.0.0 (2026-10-28)

Features

• bb-kit-dev: move scaffolding, check, and dev-instance into @bb-kit/dev (2639e07)
• bb-kit: allow a separate CLI root (32225a0)
• bb-kit: read agent text from instructions/ files (86a45bb)

Bug Fixes

• bb-kit-dev: scaffold against the current core release (641b0a1)
• bb-kit: stop runtime descendants across process groups (ffccf23)
• dev-mode: preserve stored identity and worker tool contracts (46ee911)
• scott-engineering: stop Arena rewrites repeating card labels (69a5eb8)
• workspace: resolve in-repo core consumers locally (8bc9ab7)

---

This PR was generated with Release Please. See documentation.

[devin-ai-integration]

Devin Review found 3 potential issues.

[devin-ai-integration]

🔴 Release blocked by stale lockfile

Releasing @bb-kit/dev as 1.0.0 leaves its workspace version at 0.0.0 in bun.lock. Frozen installs in CI and the release workflow fail before publishing.

Learn more

Bun's lockfile records each workspace package's version; the @bb-kit/dev entry remains 0.0.0 in the workspace lock entry. Both the CI setup and the release publisher install with --frozen-lockfile, which rejects a changed workspace manifest without a matching lock update. Publication stops before the package build.

Example: The release workflow checks out this commit and installs dependencies. Its manifest says 1.0.0, while the lock records 0.0.0, so frozen installation exits unsuccessfully instead of reaching npm publish.

Recommended fix: Regenerate and commit bun.lock with the updated packages/bb-kit-dev workspace version; verify bun install --frozen-lockfile on a clean checkout.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🔴 New plugin installation uses obsolete toolkit version

After the 1.0.0 release, bb-kit create still pins @bb-kit/dev to 0.0.0. Fresh plugin installs cannot resolve the toolkit, so scaffolding exits with an installation failure.

Learn more

SCAFFOLD_DEV_DEPENDENCIES hardcodes the exact 0.0.0 toolkit version. runCreate writes this value to each generated plugin and runs npm install, so the newly published 1.0.0 CLI continues to request the old version. The version-alignment test also fails.

Example: A user runs npx @bb-kit/dev@1.0.0 create bb-plugin-notes in a new directory. The generated manifest requires @bb-kit/dev@0.0.0, not the 1.0.0 release, and npm cannot install it when 0.0.0 is unavailable.

Recommended fix: Update the scaffold toolkit pin to 1.0.0 alongside the package manifest, then run the version-alignment test and an actual fresh scaffold install.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🔴 Devin and Review release versions disappear

The manifest drops plugins/devin and plugins/review while both remain configured release targets. The release configuration test fails, and Release Please loses their recorded versions.

Learn more

Release Please still defines both Devin and Review and Review as publishable targets. The release configuration test compares the exact target paths and versions with this manifest, so removing either key fails the repository's test job. Without their manifest entries, Release Please also has no recorded current version for those targets.

Example: On this commit, the test expects plugins/devin: 0.1.0 and plugins/review: 0.1.0, but both lookups return undefined instead.

Recommended fix: Restore both manifest entries at 0.1.0 while retaining the intended packages/bb-kit-dev version bump.

---

Was this helpful? React with 👍 or 👎 to provide feedback.