chore: release - #56
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
June 27, 2026 08:54
01301d1 to
f46eff8
Compare
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.4
Patch Changes
93017a7Thanks @johnxie! - Derive a camelCase tool name from an operation's path when the OpenAPI spec omitsoperationId(and fall back tosummaryfor the description). Enables generatingtools from specs like Taskade API v2's flat RPC routes (
POST /promptAgent). Specsthat provide
operationId(e.g. Taskade v1) are unaffected.