chore: version packages

[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 the packages will be published to npm 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

hevy-mcp@1.27.0

Minor Changes

• #512 0a592d7 Thanks @charliecreates! - Add validated structured output schemas and structuredContent to all read-only tools while preserving their existing text responses.

Patch Changes

• #504 bae0ffb Thanks @charliecreates! - Correct the MCP registration span tool count to reflect successful tool registrations.

• #509 fb00d27 Thanks @charliecreates! - Expose the user profile, workout count, exercise template catalog, and routine
  folders as discoverable MCP resources.

✨ PR Description

Purpose: Release version 1.27.0 with structured output schemas for read-only tools and new MCP resource discovery capabilities.

Main changes:

• Bumped package version from 1.26.6 to 1.27.0 in package.json
• Added structured content schemas to all read-only tools alongside text responses
• Exposed user profile, workout count, exercise templates, and routine folders as discoverable MCP resources

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how}

[gitstream-cm]

✨ PR Review

LGTM

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Review using Guidelines Learn how}

[mergify]

Queued — the merge queue status continues in this comment ↓.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.58%. Comparing base (f274d03) to head (feebb50).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #532   +/-   ##
=======================================
  Coverage   90.58%   90.58%           
=======================================
  Files          25       25           
  Lines        1115     1115           
  Branches      284      284           
=======================================
  Hits         1010     1010           
  Misses         46       46           
  Partials       59       59           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gitstream-cm]

Files in src/generated/ are generated by Kubb and must not be edited manually.
Run npm run build:client to regenerate the API client.

[gitstream-cm]

Added as any and as unknown assertions are prohibited in tool handlers.
Use InferToolParams<typeof schema> to infer parameters from the Zod schema.

[github-actions]

Unit Test Results

  1 files   23 suites   1s ⏱️
342 tests 342 ✅ 0 💤 0 ❌
343 runs  343 ✅ 0 💤 0 ❌

Results for commit feebb50.

♻️ This comment has been updated with latest results.

[charliecreates]

gitstream/block_generated_edits is blocking this release PR, but the current PR diff against main contains no src/generated/ files. The request appears to have been triggered while merging main into changeset-release/main, which made gitStream inspect inherited generated-client changes rather than a manual edit on this PR.

No safe PR-local repair is clear: regenerating the client would not change the diff that triggered the rule, and altering the gitStream policy needs an owner decision. Please update or override the block_generated_edits rule for the automated changeset-release/main branch (or dismiss the provider review) before merging.

— charlied/pr-check-repair

Review resolved

False positive from gitStream AI review on a changeset release PR that does not modify tool handlers.

[chrisdoc]

@Mergifyio refresh

[mergify]

refresh

✅ Pull request refreshed

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-10 12:21 UTC · Rule: default · triggered by rule Queue pull requests labeled 'queue'
• ❌ Checks failed · on draft merge queue: checking main (d0fa4e7) and #532 together #542
• 🚫 Left the queue — 2026-07-10 12:28 UTC · at 3475c6cd4ff558de559f2c091d9d2f355ad8ebc4

This pull request spent 7 minutes 2 seconds in the queue, including 1 minute 22 seconds running CI.

Waiting for

• check-success = "Build and test (Node 24.x)"

All conditions

• check-success = "Build and test (Node 24.x)"
• check-success = "Build and test (Node 26.x)"

Reason

The merge conditions cannot be satisfied due to failing checks

• Build and test (Node 24.x)

Failing checks:

• ❌ Build and test (Node 24.x) (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-10 12:42 UTC · Rule: default · triggered by rule Queue pull requests labeled 'queue'
• 🟠 Checks running · on draft merge queue: checking main (f274d03) and [#532 + #506 + #507] together #544
• 🚫 Left the queue — 2026-07-10 12:49 UTC · at 7984b22666c604bfea753e67fe72718d6f74185b

This pull request spent 6 minutes 49 seconds in the queue, with no time running CI.

Waiting for

• check-success = "Build and test (Node 24.x)"
• check-success = "Build and test (Node 26.x)"

All conditions

• check-success = "Build and test (Node 24.x)"
• check-success = "Build and test (Node 26.x)"

Reason

The pull request #532 has been manually updated

Requeued — the merge queue status continues in this comment ↓.

[charliecreates]

gitstream/block_generated_edits is still action_required on 7984b22. The latest PR diff only contains release artifacts (.changeset/, CHANGELOG.md, and package.json), with no src/generated/ or src/tools/ changes; gitstream/block_unsafe_tool_assertions also reported action_required for the same head.

No evidence-grounded PR change can satisfy either rule. This needs an owner to dismiss the provider requests or adjust the gitStream rules to exclude the automated changeset-release/main release PR; I did not change repository or provider configuration.

— charlied/pr-check-repair

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-10 12:49 UTC · Rule: default · triggered by rule Queue pull requests labeled 'queue'
• ✅ Checks passed · on draft merge queue: checking main (f274d03) and [#506 + #532 + #507] together #545
• ✅ Merged — 2026-07-10 12:51 UTC · at feebb5032daea04869a9908a02678e5257a7f093 · squash

This pull request spent 1 minute 52 seconds in the queue, including 1 minute 20 seconds running CI.

Required conditions to merge

• check-success = "Build and test (Node 24.x)"
• check-success = "Build and test (Node 26.x)"