Repository navigation
fix(release): publish v1.7.0, harden CI, and fix version/URL drift - #21
Merged
Merged
Conversation
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
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.0so the npm tarballs actually get replaced.Release blockers
changeset publishtried to publish the four@contextcore/*companion packages; the repoNPM_TOKENonly has access to@universal-mcp-toolkit. They are now in.changeset/config.jsonignore(the README already describes them as a separate publish line).contents: readand no git identity. Nowcontents: writeplus a bot identity, andworkflow_dispatchfor retries.pnpm check:pluginreferenced a missing script. Implemented it; it also validates the exact server pins inplugin/mcp.json, which went stale on every release.CI: faster
--lockfile-only(~0.4s).turbo/cacherestored per OS/NodeNode 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:packnow enforces:.changesetignore entriesuniversal-mcp-toolkit-monorepoentry)isMainModule(import.meta.url)entry guard in every server.well-knownversions matchingpackage.jsongithub.com/universal-mcp-toolkitURLscheck:pluginvalidates plugin versions +mcp.jsonpins.verify:published) installs the published tarballs from npm and boots them through.bin, wired into the release workflow.Bugs found and fixed
getSpawnConfig/loadPluginappended the package name to explicitnpxArgs, so MemOS launched asnpx -y @mem-os/sdk mcp @mem-os/sdk --transport stdio. Added tests.metadata.versionand.well-known/mcp-server.jsonwere stuck at0.1.0/0.2.0while packages advanced.version-packagesnow syncs them, and CI fails on drift.github.com/universal-mcp-toolkitorg instead ofMarkgatcha; fixed everywhere and guarded.universal-mcp-toolkit@1.6.27ships nodist/(same empty-publish bug as core), and its local version already matched npm sochangeset publishwould have skipped it. The 1.7.0 bump makes it publishable again;verify:publishedchecks it post-release.Release prep
This PR includes the
changeset versionoutput: core0.3.0, CLI1.7.0, bridge1.2.0, ai-sdk1.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.binsymlink.pnpm check:plugin,pnpm lint:tokens: pass.verify:publishedagainst the registry.