Skip to content

fix(ci): harden published npm smoke and rewrite the README - #3

Merged
itz4blitz merged 1 commit into
masterfrom
fix/ci-green-and-readme
Sep 6, 2026
Merged

itz4blitz merged 1 commit into
masterfrom
fix/ci-green-and-readme

Conversation

@itz4blitz

Copy link
Copy Markdown
Owner

Why

The 1.2.0 pipeline went red only on Ubuntu post-publish smoke. The inline script used spawnSync(..., { shell: true }), did not print npx stdout/stderr, and treated --help as the package args. Mac/Windows passed; Ubuntu failed 8 times with no diagnostic.

The README still advertised top-level sync, named PalamHealth, and did not explain native host files or scoped install.

What

  • scripts/smoke-published.mjs: npx --yes --package @itz4blitz/ai-tools@latest ai-tools help, no shell:true on Unix, logs every failed attempt, 12 retries
  • Post-publish job checks out the repo and runs that script
  • Tests for the help marker and retry/logging behavior
  • README rewrite (copied to packages/cli/README.md for npm): what to run, what not to run, native paths, layer / whenPathContains
  • Public CLI help no longer names PalamHealth

Release

fix(ci) → patch. semantic-release should publish @itz4blitz/ai-tools@1.2.1 with the new README.

Verify

npm run check passed locally: 182 files, coverage 89.27 / 80.03 / 88.21 / 90.25, pack smoke passed.

Post-publish smoke no longer uses shell:true or swallows npx output.
It runs `npx --package … ai-tools help`, prints stdout/stderr on
failure, and retries longer. README now describes native host files,
scoped MCP install, and that unified sync is disabled.
@itz4blitz
itz4blitz merged commit 657a17d into master Sep 6, 2026
7 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