Skip to content

release: prep v1.0.1 (privacy docs + registry mcpb package + CI auto-republish)#124

Merged
vinsonconsulting merged 1 commit into
mainfrom
release/v1.0.1
Jul 3, 2026
Merged

release: prep v1.0.1 (privacy docs + registry mcpb package + CI auto-republish)#124
vinsonconsulting merged 1 commit into
mainfrom
release/v1.0.1

Conversation

@vinsonconsulting

Copy link
Copy Markdown
Owner

What

Repo-side preparation for the 1.0.1 distribution release. No behavior change from 1.0.0 (distribution + docs only). Tags, the GitHub release, and the registry publish are held for Tuesday 2026-07-07 (holiday gate); this PR is the code/docs/CI slice.

Changes

  • Version bump to 1.0.1 across all package.json files and packages/limner-mcp/manifest.json (via pnpm sync-version; src/version.ts regenerated so limner_version reports 1.0.1).
  • Privacy Policy section added to the README plus a privacy_policies entry in the .mcpb manifest. This is a Claude Connectors Directory submission prerequisite. Covers BYO-key handling, provider calls (OpenAI / Recraft), durable memory (D1 / local SQLite), and artifact storage (R2 signed URLs).
  • CI auto-republish: a publish-registry job in build-mcpb.yml re-publishes the official MCP Registry entry on each mcpb-v* tag. Registry versions are immutable, so it derives version/asset-URL/sha256 from the tag + built bundle and tolerates an already-published version. us.limner is a DNS-verified namespace, so it authenticates with the ECDSA-P384 DNS key (github-oidc only covers io.github.*).
  • CHANGELOG 1.0.1 section.

Deliberately NOT in this PR (Tuesday follow-ups)

  • server.json gets its mcpb package entry (version 1.0.1 + asset URL + file_sha256) with the tag, since the hash only exists after the mcpb-v1.0.1 build. Kept out now so no one can accidentally burn the immutable 1.0.1 registry version early.
  • Pushing mcpb-v1.0.1 / v1.0.1 tags and the manual mcp-publisher publish.

Prereq for the CI job (Jim, one-time)

gh secret set MCP_REGISTRY_DNS_KEY < ~/.secrets/limner/mcp-registry-dns.pem

Until that secret exists the job runs green and no-ops. Confirm the mcp-publisher login dns flag names against the installed CLI during Tuesday's manual publish; adjust the workflow if the CLI surface differs.

Verification

  • pnpm -r build green; pnpm -r test = 700 passing (+6 skipped), on baseline.
  • mcpb validate packages/limner-mcp/manifest.json passes.
  • sync-version / sync-packaging drift-clean.

🤖 Generated with Claude Code

…republish)

Distribution and documentation release; no behavior change from 1.0.0.

- Bump all package versions and the .mcpb manifest to 1.0.1 (via sync-version).
- Add a Privacy Policy section to the README and a privacy_policies entry to the
  .mcpb manifest, covering BYO-key handling, provider calls, durable memory, and
  artifact storage (a Claude Connectors Directory prerequisite).
- Add a publish-registry job to build-mcpb.yml so each mcpb-v* tag re-publishes
  the official MCP Registry entry. DNS-auth (us.limner is a DNS namespace, not
  io.github, so github-oidc does not apply); gated on the MCP_REGISTRY_DNS_KEY
  secret and tolerant of an already-published immutable version.
- CHANGELOG: 1.0.1 section.

server.json's mcpb package entry (version + asset URL + file_sha256) lands with
the Tuesday tag, since the hash only exists after the mcpb-v1.0.1 build.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Jim Vinson <jim@vinson.org>
@vinsonconsulting vinsonconsulting merged commit f08bdb4 into main Jul 3, 2026
2 checks passed
@vinsonconsulting vinsonconsulting deleted the release/v1.0.1 branch July 3, 2026 18:38
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