Skip to content

release: npm 1.0.1 patch (operator CLI + worker deps) - #34

Open
ContextForgeAI wants to merge 1 commit into
mainfrom
release/npm-1.0.1
Open

release: npm 1.0.1 patch (operator CLI + worker deps)#34
ContextForgeAI wants to merge 1 commit into
mainfrom
release/npm-1.0.1

Conversation

@ContextForgeAI

Copy link
Copy Markdown
Owner

Summary

  • Bump npm semver to 1.0.1 (VERSION, @ff-occam/mcp, ff-occam, skill cards, server.json).
  • Pin HOST_RELEASE_VERSION=1.0.0 so npx @ff-occam/mcp@1.0.1 still downloads the published GitHub v1.0.0 host tarball (no signed GitHub cut required for this patch).
  • Documents npm-only scope in CHANGELOG; guarded install default (PUBLIC_DEFAULT_RELEASE_VERSION) stays 1.0.0.

After merge

  1. Run Actions → npm publish with npm_tag=latest (not rc).
  2. Smoke: npx ff-occam@1.0.1 connect → refusal + get-ff-occam pointer; npx @ff-occam/mcp@1.0.1 → downloads host 1.0.0 + installs worker deps.

Test plan

  • node --test packages/occam-mcp/test/*.test.js packages/ff-occam/test/package.test.js
  • node scripts/check-docs.mjs
  • CI green
  • npm publish workflow (manual, post-merge)

Bump npm semver to 1.0.1 for #32/#33 fixes while HOST_RELEASE_VERSION stays 1.0.0 so npx still downloads the published GitHub host tarball. Guarded install default unchanged.
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