Skip to content

fix(release): align main — bin paths normalised, 1.2.0 ready to publish - #228

Merged
beyondnetPeru merged 2 commits into
mainfrom
develop
Jul 27, 2026
Merged

fix(release): align main — bin paths normalised, 1.2.0 ready to publish#228
beyondnetPeru merged 2 commits into
mainfrom
develop

Conversation

@beyondnetPeru

Copy link
Copy Markdown
Contributor

Aligns main with develop. Last preparation step for GT-570: bin paths normalised so npm publishes without auto-correcting the manifest. Nothing published by this PR.

🤖 Generated with Claude Code

beyondnetPeru and others added 2 commits July 27, 2026 08:55
…lish

The second dry run (30271837941) was clean on everything the first one found —
LICENSE ships in all four packages, repository.url no longer normalised — but
still reported two auto-correction warnings, from a different cause:

  npm warn publish "bin[evolith-mcp]" script name was cleaned
  npm warn publish "bin[evolith]" script name was cleaned
  npm warn publish "bin[evolith-cli]" script name was cleaned

`mcp-server` and `cli` declared their bins as `./dist/main.js`; npm strips the
leading `./` on publish and warns while doing it. Declaring the normalised form
is what `npm pkg fix` would do, and it changes nothing about how the binaries
resolve — verified after the change: `cli --version` prints 1.2.0 and the MCP
server still starts.

Publishing through a warning means accepting that npm rewrites your manifest for
you. With the warnings at zero, what is declared is what is published.

Both defects fixed in this release preparation were found by rehearsal, and both
would have been permanent — npm forbids unpublishing after 72 hours. That is the
argument for `dry_run` defaulting to true, restated as evidence rather than
opinion.

Verified: 10-validate-contract-conformance, 11-validate-product-docs and
24-check-surface-parity exit 0; ci-runner governance 17/17 exit 0; `npm pack
--dry-run` reports 0 auto-correction warnings for both packages.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…ment

fix(release): normalise bin paths so npm stops auto-correcting on publish
@beyondnetPeru
beyondnetPeru requested a review from a team as a code owner July 27, 2026 13:59
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@github-actions

Copy link
Copy Markdown

📊 Bilingual Coverage Impact

PR Changes

  • Paired EN/ES files modified: 0
  • New EN files needing ES translation: 0

Repository Coverage

Metric Value
Total EN files 522
Total ES files 496
Paired files 0
Coverage 0%

Good: All EN changes have ES counterparts.


Generated by GitHub Actions

@beyondnetPeru
beyondnetPeru merged commit 9a82d9f into main Jul 27, 2026
60 of 64 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