Skip to content

chore: update dependencies#432

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

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

Conversation

@poe-code-agent

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

Copy link
Copy Markdown
Contributor

Summary

  • Refresh npm lockfile dependencies to the latest compatible versions.
  • Align the E2B sandbox kill() type with the updated e2b SDK return type.
  • Accept the current ACP end_turn stop reason emitted by updated agents.

Validation

  • npx vitest run packages/poe-acp-client/src/acp-client-unified.test.ts -t "accepts current ACP stopReason"
  • npx vitest run packages/poe-acp-client/src/acp-client-unified.test.ts -t "rejects prompt responses"
  • npm run build -w @poe-code/poe-acp-client
  • npm run build
  • npm run lint
  • npm test
  • push hook: npm run lint:packages
  • push hook: npm test

Notes

  • npm audit still reports the existing gray-matter/js-yaml advisory that requires a semver-major gray-matter downgrade, plus an agent-stash nested esbuild advisory that npm audit fix did not resolve within current compatible ranges.

@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

Comment thread package-lock.json
"license": "ISC",
"engines": {
"node": "^20.17.0 || >=22.9.0"
"node": "^22.22.2 || ^24.15.0 || >=26.0.0"

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.

Non-blocking: npm ci on Node 20 now emits an EBADENGINE warning here because @opencode-ai/plugin@1.17.9 pulls effect@4.0.0-beta.74ini@7.0.0, which requires Node >=22.22.2. It still installed locally under npm 10, so I don't think this should block the lockfile refresh.

@poe-code-agent
poe-code-agent Bot force-pushed the chore/update-dependencies-compatible branch from 00035cb to 24c8991 Compare June 22, 2026 08:24

@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

@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: 24c8991b48

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

export type RequestId = null | number | string;

export type StopReason = "completed" | "cancelled" | "max_tokens";
export type StopReason = "completed" | "end_turn" | "cancelled" | "max_tokens";

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 Accept all current ACP stop reasons

When an ACP v1 agent returns max_turn_requests after hitting its per-turn request cap or refusal, the client still rejects the prompt response because this union and validStopReasons exclude them. The ACP v1 schema lists end_turn, max_tokens, max_turn_requests, refusal, and cancelled as StopReason values (https://agentclientprotocol.com/protocol/v1/schema#stopreason), so this partial update still breaks valid agents in those stop paths.

Useful? React with 👍 / 👎.

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.

0 participants