chore(deps): bump actions/setup-node from 4 to 6#1
Merged
Conversation
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v4...v6) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
bbingz
added a commit
that referenced
this pull request
May 6, 2026
…from bench output Followup #1 from the bench commit (a976f83): polycli previously had prompting skills for gemini/kimi/qwen/minimax but not for claude, so the claude provider path got no per-provider prompt scaffolding. The pilot exposed this gap. The new skill encodes claude-specific guidance: CLAUDE.md does not propagate to the child session (verified empirically by the bench), same model family means no need to over-specify output format, sessions are stateless by default, and errors may surface as subtype: "error". Also hardens the bench runner: scripts/bench-vs-bare-cli.mjs now sanitizes stored stdout/stderr/parsedJson by replacing $HOME with ~ before writing results JSON. The first published run leaked a maintainer-local path because qwen rescue output hallucinated absolute paths under the bench cwd; open-source-hygiene.test.mjs caught it. Existing results-2026-04-29.json is retroactively sanitized. npm test: 287/287 passing.
bbingz
added a commit
that referenced
this pull request
Jun 2, 2026
…ssion parse Addresses the pre-merge Codex review gate for PR #6. - resume flag (real bug): buildKimiInvocation emitted `-r <id>` for resume-by-id, but kimi-code v0.6.0 has NO `-r` flag — `kimi --help` shows resume-by-id is `-S, --session [id]` (continue-last `-C` is correct). `-r` would be rejected at runtime, and the path IS reachable (`polycli rescue --provider kimi --resume <id>` threads through to it, per integration test). Switch to `--session <id>`; update unit + integration assertions and the comment. - session-id parse (hardening): parseKimiStreamText adopted session_id from ANY `role:"meta"` event; the documented source is specifically the `{role:"meta", type:"session.resume_hint", session_id:"session_<uuid>"}` event. Require `type === "session.resume_hint"` so an unrelated meta event carrying a session_id is not promoted. Add a regression test. - fragile review test (latent failure exposed by committing the migration): two `review --base HEAD~1 --scope branch` integration tests asserted `doesNotMatch(argv.join(" "), /--no-thinking|--max-steps.../)`. The reviewed diff is embedded in the single `-p <prompt>` element and legitimately mentions those removed flags as deleted-code text, so the substring check false-positives on this very migration's diff. Check the flags as discrete argv tokens (argv.includes) instead — same intent, no false positive. Codex false-positives (verified, NOT changed): #1 `-p`+`--plan/--auto/--yolo` combination is latent-only — no caller injects those (review extraArgTokens empty; prompt-runtime kimi-ask is plain `-p`); #4 the `~/.kimi/` literal is an intentional migration-history comment, code uses `~/.kimi-code/`. npm test 452/452 (was 451; +1 session-parse regression). 5 bundles byte-identical.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps actions/setup-node from 4 to 6.
Release notes
Sourced from actions/setup-node's releases.
... (truncated)
Commits
48b55a0Update Node.js versions in versions.yml and bump package to v6.4.0 (#1533)ab72c7eUpgrade@actionsdependencies (#1525)53b8394Bump minimatch from 3.1.2 to 3.1.5 (#1498)54045abScope test lockfiles by package manager and update cache tests (#1495)c882bffReplace uuid with crypto.randomUUID() (#1378)774c1d6feat(node-version-file): support parsingdevEnginesfield (#1283)efcb663fix: remove hardcoded bearer (#1467)d02c89dFix npm audit issues (#1491)6044e13Docs: bump actions/checkout from v5 to v6 (#1468)8e49463Fix README typo (#1226)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)