Skip to content

fix: align plugin-lib pin to v0.8.5 #199 #200

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
four-bytes-robby merged 2 commits into from
Jul 6, 2026
Merged

fix: align plugin-lib pin to v0.8.5 #199 #200

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1548eea
fix: align plugin-lib pin to v0.8.5 #199
four-bytes-robby Jul 6, 2026
00c2e43
fix: regenerate bun.lock for v0.8.5 pin #199
four-bytes-robby Jul 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"

@cubic-dev-ai cubic-dev-ai Bot Jul 6, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>

```
When plugin-lib changes are merged:
1. Bump version in plugin-lib's `package.json`
2. Tag: `git tag v0.8.6 && git push --tags`
2. Tag: `git tag v0.8.5 && git push --tags`
3. Update all dependent plugins' `package.json` + `bun.lock` to new tag
Comment thread
coderabbitai[bot] marked this conversation as resolved.

**Local dev:** Uses `bun link` to point `node_modules/@four-bytes/opencode-plugin-lib` at the local source `~/four-opencode-plugin-lib`:
Expand Down
4 changes: 2 additions & 2 deletions bun.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading