Skip to content

Release: @genclass/mcp 0.2.0 and @genclass/runtime 0.3.0-beta.2 - #104

Merged
Karanvir1729 merged 2 commits into
mainfrom
release-mcp-0.2.0-runtime-0.3.0-beta.2
Oct 25, 2026
Merged

Karanvir1729 merged 2 commits into
mainfrom
release-mcp-0.2.0-runtime-0.3.0-beta.2

Conversation

@Karanvir1729

Copy link
Copy Markdown
Collaborator

What

Version bumps for the two releases the end-to-end walkthrough (#103) showed are needed:

  • @genclass/mcp 0.1.0 → 0.2.0. The 0.1.0 on npm is an earlier build: eight tools, no genclass_scan, no GENCLASS_REPORT. The changelog's first section (scan, the dashboard mirror and its two fixes, explore's bookkeeping filter, the newest-line setup) ships first in 0.2.0. npm run sync -w @genclass/mcp updated every pinned launcher (README, plugin, server.json, the root manifests, src/http.ts); the dashboard's own install line too.
  • @genclass/runtime 0.3.0-beta.1 → 0.3.0-beta.2. package.json, src/version.ts, the changelog heading over the unreleased section (scan, the newest-line install path, the fixes since beta.1).
  • The lockfile's two workspace versions, nothing else.

Release steps after the merge

  1. git tag v0.3.0-beta.2 <merge commit> && git push origin v0.3.0-beta.2 runs release.yml; git tag mcp-v0.2.0 <merge commit> && git push origin mcp-v0.2.0 runs release-mcp.yml. Both publish through the npm-publish environment, which asks its reviewers to approve each run.
  2. Once jsDelivr serves @genclass/runtime@0.3.0-beta.2: RUNTIME_ON_NPM in telemetry-worker/wrangler.toml and SNIPPET_RUNTIME in telemetry-worker/src/pages.ts, then a deploy (not in this PR, as the worker's comment says).

Checks

  • @genclass/runtime: typecheck, build, npx vitest run (CI's set): 1209 pass, 14 skipped (the model-parity tests).
  • @genclass/mcp: typecheck, build, suite: 132 pass; test/manifests.test.ts after the sync: 21 pass.
  • telemetry-worker: 332 pass.

🤖 Generated with Claude Code

Karanvir1729 and others added 2 commits October 25, 2026 17:05
@genclass/mcp 0.2.0: the 0.1.0 on npm is an earlier build (eight tools, no genclass_scan, no GENCLASS_REPORT), so
everything in the changelog's first section ships first in 0.2.0; the version, its pinned launchers in the README,
the plugin, server.json and the root manifests (npm run sync), the dashboard's own install line, and the changelog's
heading. @genclass/runtime 0.3.0-beta.2: the version in package.json and src/version.ts, the changelog's heading over
the unreleased section (scan, the newest-line install path, the agent link's and analytics' fixes). The lockfile's
two workspace versions.

Tags v0.3.0-beta.2 and mcp-v0.2.0 on this commit run release.yml and release-mcp.yml. After npm has the runtime:
RUNTIME_ON_NPM and SNIPPET_RUNTIME in telemetry-worker, then a deploy.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…t exactly

packages/playwright and packages/genclass-runtime depend on the published @genclass/runtime 0.3.0-beta.1, not the
workspace; with the workspace at 0.3.0-beta.2 the lock needs their nested copies from the registry, as npm install
writes them (npm ci refused the hand-edited lock).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@Karanvir1729
Karanvir1729 merged commit 1221450 into main Oct 25, 2026
13 of 14 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