fix: align plugin-lib pin to v0.8.5 #199 - #200
Conversation
📝 WalkthroughWalkthroughAGENTS.md documentation updated to correct the pinned GitHub tag reference for the ChangesDocumentation Fix
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 `@AGENTS.md`:
- Around line 56-61: The dependency tag was updated in the guidance, but the
lockfile still pins `@four-bytes/opencode-plugin-lib` to the old v0.8.4 reference,
so refresh bun.lock to match the new v0.8.5 tag. Update the lock entry generated
for the dependency so it resolves to the new tag, and keep the package.json note
in AGENTS.md consistent with the regenerated lockfile.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 1 file
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="AGENTS.md">
<violation number="1" location="AGENTS.md:56">
P1: The AGENTS.md documentation was updated to state that `package.json` pins `@four-bytes/opencode-plugin-lib` to `#v0.8.5`, but the `bun.lock` file was not regenerated or updated in this PR. The lockfile still resolves to the old commit (`8b78211` / `v0.8.4`), which means CI and local installs may continue to fetch the previous version despite the documented claim. Since AGENTS.md itself instructs maintainers to "Update all dependent plugins' `package.json` + `bun.lock` to new tag," the lockfile should be regenerated with `bun install` so the resolved commit matches the declared `v0.8.5` tag.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| **CI:** `package.json` pins to a GitHub tag: | ||
| ```json | ||
| "@four-bytes/opencode-plugin-lib": "github:four-bytes/four-opencode-plugin-lib#v0.8.6" | ||
| "@four-bytes/opencode-plugin-lib": "github:four-bytes/four-opencode-plugin-lib#v0.8.5" |
There was a problem hiding this comment.
P1: The AGENTS.md documentation was updated to state that package.json pins @four-bytes/opencode-plugin-lib to #v0.8.5, but the bun.lock file was not regenerated or updated in this PR. The lockfile still resolves to the old commit (8b78211 / v0.8.4), which means CI and local installs may continue to fetch the previous version despite the documented claim. Since AGENTS.md itself instructs maintainers to "Update all dependent plugins' package.json + bun.lock to new tag," the lockfile should be regenerated with bun install so the resolved commit matches the declared v0.8.5 tag.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At AGENTS.md, line 56:
<comment>The AGENTS.md documentation was updated to state that `package.json` pins `@four-bytes/opencode-plugin-lib` to `#v0.8.5`, but the `bun.lock` file was not regenerated or updated in this PR. The lockfile still resolves to the old commit (`8b78211` / `v0.8.4`), which means CI and local installs may continue to fetch the previous version despite the documented claim. Since AGENTS.md itself instructs maintainers to "Update all dependent plugins' `package.json` + `bun.lock` to new tag," the lockfile should be regenerated with `bun install` so the resolved commit matches the declared `v0.8.5` tag.</comment>
<file context>
@@ -53,11 +53,11 @@ Issues → Branch → PR → Merge (feature workflow)
**CI:** `package.json` pins to a GitHub tag:
```json
-"@four-bytes/opencode-plugin-lib": "github:four-bytes/four-opencode-plugin-lib#v0.8.6"
+"@four-bytes/opencode-plugin-lib": "github:four-bytes/four-opencode-plugin-lib#v0.8.5"
When plugin-lib changes are merged:
</file context>
</details>
|
@coderabbitai @cubic-dev-ai Fixed in 00c2e43 — |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
git log --oneline -5
git show --stat 00c2e43 2>/dev/null | head -20
echo "---"
grep -n "opencode-plugin-lib" bun.lock | head -20Length of output: 1324 Confirmed — commit 00c2e43 regenerates |
1 participant
Description
Pins
@four-bytes/opencode-plugin-libto tagv0.8.5(commit04ea32f) onfour-bytes/four-opencode-plugin-lib.Changes
v0.8.4tov0.8.5v0.8.5Background
The
v0.8.5tag was created onfour-bytes/four-opencode-plugin-libto resolve the pinned dependency. This PR aligns the brain's plugin-lib dependency to that tag.Closes #199
Summary by cubic
Pins
@four-bytes/opencode-plugin-libto v0.8.5 to match the released tag and avoid CI/install mismatches. Regeneratesbun.lockand updates docs.@four-bytes/opencode-plugin-libtogithub:four-bytes/four-opencode-plugin-lib#v0.8.5and regeneratebun.lock.AGENTS.mdreferences to v0.8.5.Written for commit 00c2e43. Summary will update on new commits.
Summary by CodeRabbit