[nborges-aws]

Description

Pin verification to the CLI minimum Node version, 20.12.0. Update the stdin regression test to wait for the READY marker and tolerate the warning Node 20 may print before it.

Upgrading minimum Node version should be considered as the long term fix for this issue. This PR aims to unblock the workflow in the interim

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

How have you tested the change?

• I ran bun test
• I ran the relevant end-to-end tests with bun run test:e2e, or explained why they are not applicable
  (CI does not run them for you)
• I ran bun run typecheck
• I ran bun run lint:check
• I ran bun run format:check
• I ran bun run audit
• I ran bun run secrets:check
• I ran bun run build
• If I modified src/assets/, I updated affected snapshots with bun test <test-file> --update-snapshots and committed them
• If I re-recorded fixtures or golden files, every change beyond account identifiers is explained
  by this PR
• This PR does not change command.md (the release workflow regenerates it)

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Package Tarball

aws-agentcore-1.0.2.tgz

How to install

gh release download pr-2777-tarball --repo aws/agentcore-cli --pattern "*.tgz" --dir /tmp/pr-tarball
npm install -g /tmp/pr-tarball/aws-agentcore-1.0.2.tgz

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Looks good

Checked against base v1.x. Both changes hold up:

• .github/workflows/verify.yml — the pin (20.12.0) matches engines.node (>=20.12.0), the action SHA (949feb2… / v7.1.0) is the same one already used in canary.yml, e2e-test.yml, and pr-automation.yml, and setup-node is already proven on the same image:windows-1.0 CodeBuild runner class by e2e-test.yml. Nothing else in the job depends on a newer Node — build/pack/compile/smoke-test all run through Bun, and the Codecov action brings its own runtime — so dropping the ambient Node to 20.12 only affects the tests that spawn node (src/io/source.test.ts, src/io/exec.test.ts, src/io/exec-arguments.test.ts), none of which use post-20 syntax or APIs. Both verify callers (ci.yml, release-main-and-preview.yml) pick up the pin, and both jobs in the file were updated.
• src/io/source.test.ts — gating on the READY marker instead of the first stderr chunk is strictly more correct than the old once(child.stderr, "data"), and rejecting on early close/error turns a would-be timeout into a diagnosable failure with the captured stderr. The late-rejection of an already-settled promise by the close listener is a harmless no-op, and the subsequent once(child, "close") still gets its event.

Two non-blocking observations, take or leave:

• expect(errors).toContain("READY\n") (src/io/source.test.ts) is now tautological — await ready only resolves when errors includes that marker, so the assertion cannot fail. The real regression signal is still code === 0 and output === "late value", which do catch a child that threw after printing READY, so coverage is intact; the line is just redundant.
• The comment "Node 20 can warn while importing Ink" doesn't name the warning. Naming it (or linking the issue) would let a future reader tell when it's safe to tighten the assertion back to an exact match, especially given the PR frames the Node-version bump as the long-term fix.

One coverage trade-off worth being aware of: verify is the only workflow that runs bun test, so after this PR the node branch of this regression test runs only on 20.12.0 — the newer Node the runners previously provided is no longer exercised by it (e2e runs Node 24, but not this test). If cross-version behavior of the stdin path matters, a two-entry Node matrix would be the follow-up; the interim unblock as written is fine.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.50%. Comparing base (ddb6807) to head (692a87e).
⚠️ Report is 1 commits behind head on v1.x.

Additional details and impacted files

@@           Coverage Diff           @@
##             v1.x    #2777   +/-   ##
=======================================
  Coverage   96.50%   96.50%           
=======================================
  Files         709      709           
  Lines       58865    58865           
=======================================
+ Hits        56805    56806    +1     
+ Misses       2060     2059    -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.