Skip to content

feat(scripts): add push to mcp-node on release #4784

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

shortcuts
Copy link
Member

🧭 What and Why

🎟 JIRA Ticket:

Changes included:

This PR adds mcp-node to the repository to spread the specs to, it also updates the support for JSON output as this is what's expected there.

@shortcuts shortcuts self-assigned this Apr 25, 2025
@algolia-bot
Copy link
Collaborator

algolia-bot commented Apr 25, 2025

✔️ Code generated!

Name Link
🪓 Triggered by d9a0e44f7b8e0222a267f4c2d4c08aa5fba0ff37
🍃 Generated commit 86a24249684cb45b7b2b1a7a58376b6048c0ab10
🌲 Generated branch generated/feat/scripts-push-to-mcp-node
📊 Benchmark results

Benchmarks performed on the method using a mock server, the results might not reflect the real-world performance.

Language Req/s
go 1646
javascript 1633
php 1500
csharp 1391
java 1084
python 1063
ruby 804
swift 441
scala 23

@shortcuts shortcuts marked this pull request as ready for review April 28, 2025 08:49
@shortcuts shortcuts requested a review from a team as a code owner April 28, 2025 08:49
@@ -57,6 +57,7 @@ get:
tags:
- abtest
operationId: listABTests
x-mcp-tool: true
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as per @kombucha's comment this might be easier/better to handle at the mcp repository level, unless we see some documentation purposes that we want to reflect on our API reference pages?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could be indeed reflected in the documentation at some point! I'd stick with your solution !

Copy link
Collaborator

@millotp millotp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gg !

Copy link
Contributor

@morganleroi morganleroi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

God save the OpenAPI spec!

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.

4 participants