Skip to content

fix(release): publish v1.7.0, harden CI, and fix version/URL drift - #21

Merged
Markgatcha merged 2 commits into
mainfrom
feat/ci-hardening
Nov 3, 2026
Merged

Markgatcha merged 2 commits into
mainfrom
feat/ci-hardening

Conversation

@Markgatcha

Copy link
Copy Markdown
Owner

Why

Fixes the release blockers found while shipping the #18 packaging fix, speeds up CI, and fixes several bugs found during the audit. Also prepares v1.7.0 so the npm tarballs actually get replaced.

Release blockers

  • Every release aborted with E404. changeset publish tried to publish the four @contextcore/* companion packages; the repo NPM_TOKEN only has access to @universal-mcp-toolkit. They are now in .changeset/config.json ignore (the README already describes them as a separate publish line).
  • Release workflow could not push tags. It had contents: read and no git identity. Now contents: write plus a bot identity, and workflow_dispatch for retries.
  • pnpm check:plugin referenced a missing script. Implemented it; it also validates the exact server pins in plugin/mcp.json, which went stale on every release.

CI: faster

before after
PR build jobs 6 matrix legs + rolling + token-budget 4 matrix legs + 1 packaging job
Full builds per PR 10 6
Packaging checks 6x (one per matrix leg) 1x on Linux
Lockfile check full install --lockfile-only (~0.4s)
Turbo cache none .turbo/cache restored per OS/Node
Rolling Node every PR main/schedule only

Node coverage is still 22 + 24, and macOS/Windows coverage is preserved. The packaging job runs verify:pack, verify:launch, lint, token budgets, and plugin checks once.

New guards

  • verify:pack now enforces:
    • release scopes and .changeset ignore entries
    • pending changesets referencing real, non-ignored workspace packages (this would have caught the stale universal-mcp-toolkit-monorepo entry)
    • the shared isMainModule(import.meta.url) entry guard in every server
    • server metadata / .well-known versions matching package.json
    • no stale github.com/universal-mcp-toolkit URLs
  • check:plugin validates plugin versions + mcp.json pins.
  • New post-publish smoke test (verify:published) installs the published tarballs from npm and boots them through .bin, wired into the release workflow.

Bugs found and fixed

  1. Plugin npx args duplicated. getSpawnConfig/loadPlugin appended the package name to explicit npxArgs, so MemOS launched as npx -y @mem-os/sdk mcp @mem-os/sdk --transport stdio. Added tests.
  2. Every server reported a stale version. metadata.version and .well-known/mcp-server.json were stuck at 0.1.0/0.2.0 while packages advanced. version-packages now syncs them, and CI fails on drift.
  3. Wrong repository URLs. 48 files pointed at the non-existent github.com/universal-mcp-toolkit org instead of Markgatcha; fixed everywhere and guarded.
  4. The published CLI is empty. universal-mcp-toolkit@1.6.27 ships no dist/ (same empty-publish bug as core), and its local version already matched npm so changeset publish would have skipped it. The 1.7.0 bump makes it publishable again; verify:published checks it post-release.

Release prep

This PR includes the changeset version output: core 0.3.0, CLI 1.7.0, bridge 1.2.0, ai-sdk 1.1.0, and all 31 servers patched. Plugin manifests and pins are updated to match.

Verification

  • pnpm build, pnpm typecheck, pnpm test, pnpm lint:ox: pass.
  • pnpm verify:pack: 35 packages / 33 bins, tarball contents + release policy checked.
  • pnpm verify:launch: all bins boot through a .bin symlink.
  • pnpm check:plugin, pnpm lint:tokens: pass.
  • Post-merge I will publish via the release workflow and run verify:published against the registry.

Mark Gatcha added 2 commits November 3, 2026 12:49
- Ignore the @contextcore/* companion packages in changesets; the NPM_TOKEN cannot publish that scope and every release aborted with E404 mid-publish.
- Add a workspace release-policy check: publish scopes, ignored-package dependencies, pending changeset packages, and the shared isMainModule entry guard.
- Add check:plugin to validate plugin manifest versions and the exact server pins in plugin/mcp.json, which otherwise go stale after a release.
- Add check:plugin and verify:published post-publish smoke tests, and wire them into CI/release.
- Fix plugin-loader duplicating explicit npxArgs for companion entries such as MemOS, with tests.
- Speed CI up: one packaging job instead of packaging checks in every matrix leg, 4 matrix legs instead of 6, Turborepo cache restore, lockfile-only drift check, rolling Node only on main/schedule, and a single install in the release workflow.
- Give the release workflow contents:write, a git identity for tags, and workflow_dispatch for retries.
- changeset version: core 0.3.0, CLI 1.7.0, bridge 1.2.0, ai-sdk 1.1.0, all servers patched
- sync server metadata and .well-known manifests to the new package versions (changeset version only edits package.json)
- point every server homepage/repository/documentation URL at Markgatcha/universal-mcp-toolkit; they referenced a non-existent org
- update plugin manifests to 1.7.0 and re-pin plugin/mcp.json to the new server versions
- add sync-package-versions.mjs and version/metadata/URL drift checks to verify-packages
Copilot AI balanced review requested due to automatic review settings November 3, 2026 18:01

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-03T18:05:40.984787Z 2520c7b PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@Markgatcha
Markgatcha merged commit 6629385 into main Nov 3, 2026
10 checks passed
@Markgatcha
Markgatcha deleted the feat/ci-hardening branch November 3, 2026 18:22
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.

2 participants