Skip to content

chore: update compatible dependencies#389

Open
poe-code-agent[bot] wants to merge 1 commit into
mainfrom
chore/update-compatible-dependencies-20260608
Open

chore: update compatible dependencies#389
poe-code-agent[bot] wants to merge 1 commit into
mainfrom
chore/update-compatible-dependencies-20260608

Conversation

@poe-code-agent

@poe-code-agent poe-code-agent Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Updated npm lockfile dependencies to the latest versions allowed by current compatible ranges.
  • Kept @opencode-ai/plugin on the latest 1.15 patch line for opencode-poe-auth to avoid the Node 22+ engine requirement introduced through the 1.16 dependency chain.
  • Refreshed the runtime help snapshot that was stale after validation.

Validation

  • npm run build
  • npm run lint
  • npm test
  • npm audit --omit=optional

@poe-code-agent poe-code-agent Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

LGTM

@garethpaul garethpaul force-pushed the chore/update-compatible-dependencies-20260608 branch from 0a5f9c3 to b68af49 Compare June 9, 2026 17:14

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b68af498a5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

},
"devDependencies": {
"@opencode-ai/plugin": "^1.3.0"
"@opencode-ai/plugin": "~1.15.13"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Constrain the published plugin peer range

This only pins the workspace dev/test copy of @opencode-ai/plugin; it is not installed for consumers of the published package, while the peer range above still accepts *. In an OpenCode 1.16+ project, or when npm resolves the missing peer during npm install opencode-poe-auth, the package can still be paired with the Node-22-only dependency chain this change is trying to avoid. If 1.16 is incompatible with the supported Node 20 path, the peer range needs the same upper bound or the peer should be made optional/non-resolving.

Useful? React with 👍 / 👎.

@poe-code-agent poe-code-agent Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant