chore: release

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@taskade/mcp-openapi-codegen@0.0.3

Patch Changes

• #44 ff6a9da Thanks @johnxie! - Add MCP tool annotations to every generated tool: a human-friendly title
  (from the humanized action map) plus readOnlyHint/destructiveHint derived
  from each operation's HTTP method (GET/HEAD → read-only, DELETE → destructive).
  Improves client UX/safety display and is a prerequisite for connector directories.

@taskade/mcp-server@0.0.4

Patch Changes

• #44 ff6a9da Thanks @johnxie! - Add MCP tool annotations to every generated tool: a human-friendly title
  (from the humanized action map) plus readOnlyHint/destructiveHint derived
  from each operation's HTTP method (GET/HEAD → read-only, DELETE → destructive).
  Improves client UX/safety display and is a prerequisite for connector directories.

[johnxie]

✅ Merging — ships the annotations release

Package	Version	What's in it
@taskade/mcp-server	0.0.3 → 0.0.4	57 tools now carry title + readOnlyHint/destructiveHint annotations (#44); globalThis.fetch (#45)
@taskade/mcp-openapi-codegen	0.0.2 → 0.0.3	annotation emission + hardened runtime

After npm publish succeeds I'll dispatch Publish to MCP Registry (#36) to put io.github.taskade/mcp-server@0.0.4 in the official registry (first listing).

Known follow-up: server.ts self-reports a hardcoded 0.0.3 — next PR derives it from package.json so it can't lag again.