Skip to content

test: packed one-copy check installs with npm and no peers, as users do - #435

Merged
ualtinok merged 1 commit into
mainfrom
test/smoke-copy-count-npm
Oct 21, 2026
Merged

ualtinok merged 1 commit into
mainfrom
test/smoke-copy-count-npm

Conversation

@antauth-alfonso

@antauth-alfonso antauth-alfonso Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

On 21 Oct the 2.2.2 release PR failed in the packed smoke because Bun resolved Pi's peer tree (pi-ai pulls the AWS SDK), and AWS had published client-bedrock-runtime and core before the @aws-sdk/types and credential-provider-process versions they require. npm with --omit=peer installs no AWS packages. The copy-count step now uses npm with --omit=peer --omit=dev --ignore-scripts, from the same packed tarballs, Core forced through overrides; the rest of the smoke stays on Bun. Still red when OpenCode pins claustrum-client 0.11.0 against Core's 0.12.0 (both copies named).


Summary by cubic

Switches the packed one-copy install smoke test from Bun to npm so it matches how users actually install OpenCode and Pi, making the check resilient to inconsistent registry states.

  • bun install --omit peer still resolves Pi's peer tree, which dragged in the AWS SDK and broke the 2.2.2 release when AWS published a package before its own dependencies.
  • The step now runs npm install --omit=peer --omit=dev --ignore-scripts --no-audit --no-fund from the same packed tarballs, with Core forced to its packed tarball through overrides.
  • The rest of the smoke stays on Bun.
  • The check is still red when OpenCode pins claustrum-client 0.11.0 against Core's 0.12.0.

Written for commit 95941af. Summary will update on new commits.

View guided diff Turn on auto-fix

@antauth-alfonso antauth-alfonso Bot closed this Oct 21, 2026
@antauth-alfonso antauth-alfonso Bot reopened this Oct 21, 2026
The one-copy check for @cortexkit/claustrum-client and subc-client ran
'bun install --production --omit peer', which still resolves Pi's peer
tree (pi-ai -> AWS SDK). A freshly published AWS package whose own
dependencies were not yet on npm broke the 2.2.2 release CI there.
Users install with npm, and npm --omit=peer installs no AWS packages,
so this step now runs npm install --omit=peer --omit=dev
--ignore-scripts --no-audit --no-fund from the same packed tarballs,
with Core forced to its packed tarball through overrides. The rest of
the smoke stays on Bun.
@ualtinok
ualtinok force-pushed the test/smoke-copy-count-npm branch from 4ff0a41 to 95941af Compare October 21, 2026 22:41
@ualtinok
ualtinok merged commit 95941af into main Oct 21, 2026
12 checks passed
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