Skip to content

fix: sync version to 0.0.3 and correct root license to MIT - #38

Merged
johnxie merged 1 commit into
mainfrom
fix/version-and-license-sync
Jun 5, 2026
Merged

fix: sync version to 0.0.3 and correct root license to MIT#38
johnxie merged 1 commit into
mainfrom
fix/version-and-license-sync

Conversation

@johnxie

@johnxie johnxie commented Jun 5, 2026

Copy link
Copy Markdown
Member

What & why

Four-way version drift + an incorrect root license, all verified on main:

Source Before After
packages/server/src/server.ts:16 (self-reported to clients) 0.0.1 0.0.3
packages/server/server.json (registry manifest, ×2) 0.0.2 0.0.3
root package.json version 0.0.1 0.0.3
root package.json license UNLICENSED MIT

The published npm package is already 0.0.3; this aligns every other source to it so the server reports the correct version to clients/registries, and fixes the UNLICENSED root (the server package + LICENSE file are MIT).

Zero-regression

  • Value-only edits (version strings + license); no logic changes.
  • Both JSON files validate; yarn lint clean.
  • Prerequisite for the MCP Registry publish (clean package-ownership/version check).

Notes

  • Optional follow-up: derive server.ts version from package.json so it can't drift again.

… MIT

- server.ts self-reported 0.0.1, server.json 0.0.2, package.json 0.0.3 (four-way drift)
- root package.json license was UNLICENSED while the server + LICENSE file are MIT
- align all version strings to the published 0.0.3 and set root license to MIT
@johnxie
johnxie requested a review from Copilot June 5, 2026 11:02
@changeset-bot

changeset-bot Bot commented Jun 5, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: c5b44a2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

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.

Pull request overview

Aligns repository metadata with the already-published @taskade/mcp-server@0.0.3 by removing version drift across the server’s self-reported version, registry manifest, and the monorepo root package metadata, and correcting the root license to match the MIT LICENSE file.

Changes:

  • Update TaskadeMCPServer self-reported version to 0.0.3.
  • Update packages/server/server.json manifest version fields to 0.0.3.
  • Update root package.json version to 0.0.3 and license to MIT.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
packages/server/src/server.ts Bumps the server’s reported version to 0.0.3 for clients.
packages/server/server.json Synchronizes the MCP registry manifest version fields to 0.0.3.
package.json Updates monorepo root version to 0.0.3 and sets license to MIT.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@johnxie

johnxie commented Jun 5, 2026

Copy link
Copy Markdown
Member Author

✅ Validation & QA — ready to merge

Copilot reviewed and generated no comments. Re-validated against the codebase:

Check Result
version drift (server.ts / server.json / package.json) all → 0.0.3
root license vs LICENSE file UNLICENSEDMIT
JSON validity both files parse ✓
yarn lint clean ✓

Value-only edits, no logic. Confidence: high · zero regression. Merging.

@johnxie
johnxie merged commit ddcfa00 into main Jun 5, 2026
1 check passed
@johnxie
johnxie deleted the fix/version-and-license-sync branch June 5, 2026 11:55
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