- 
                Notifications
    You must be signed in to change notification settings 
- Fork 45
release: v0.7.5 #331
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
release: v0.7.5 #331
Conversation
…velop Rebase release 0.7.2 to develop
* ci: ignoring changeset verification for merges to release or main * chore: reordering
docs: clarify details for auth implementation
Swapping the code owner from the broader graph tooling team to the more newly scoped ai-runtime team
* ci: adding a workflow to autogen main to develop sync pr * ci: adding a work dispatch trigger for testing * chore: adjusting bool check for consistency
…-pr- Sync main → develop (resolve conflicts)
fix: Add missing token propagation for execute tool
…-pr-299 Sync main → develop (resolve conflicts)
…-pr-269 Sync main → develop (resolve conflicts)
Sync main → develop (PR #304)
Update snapshots in custom_scalar_map.rs
Sync main → develop (PR #310)
test: hardcoded version strings in tests
Sync main → develop (PR #315)
* chore: updating step name * chore: adding needed permissions
* ci: updating sync workflow to pull pr num and url correctly * chore: adding label to skip changeset check * chore: fixing merge conflict
* test: adding a basic manual e2e test for mcp server * chore: adding missing changeset file * Re-run ai style check * Re-run ai style check * chore: removing exec since it interferes with trap
Sync main → develop (PR #308)
This commit finalizes the work needed for prepping releases using automatic scripts.
The validate tool was parsing the operation passed in to it against the schema but it wasn't performing the validate function on the `ExecutableDocument` returned by the Parser. This led to cases where missing required arguments were not caught by the Tool. This change also updates the input schema to the execute tool to make it more clear to the LLM that it needs to provide a valid JSON object
| ✅ Docs preview readyThe preview is ready to be viewed. View the preview File Changes 0 new, 1 changed, 0 removedBuild ID: 239652b6674505dc9055e47b URL: https://www.apollographql.com/docs/deploy-preview/239652b6674505dc9055e47b | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
| Opened sync PR main → develop: #333 Merge status: clean ✅ | 
[0.7.5] - 2025-09-03
🐛 Fixes
fix: Validate ExecutableDocument in validate tool - @swcollard PR #329
Contains fixes for #327
The validate tool was parsing the operation passed in to it against the schema but it wasn't performing the validate function on the ExecutableDocument returned by the Parser. This led to cases where missing required arguments were not caught by the Tool.
This change also updates the input schema to the execute tool to make it more clear to the LLM that it needs to provide a valid JSON object
🛠 Maintenance
test: adding a basic manual e2e test for mcp server - @alocay PR #320
Adding some basic e2e tests using mcp-server-tester. Currently, the tool does not always exit (ctrl+c is sometimes needed) so this should be run manually.
How to run tests?
Added a script
run_tests.sh(may need to runchmod +xto run it) to run tests. Basic usage found via./run_tests.sh -h. The script does the following:apollo-mcp-serverbinary exists. If not, it builds the binary viacargo build --release.mcp-server-tester) and replaces all<test-dir>placeholders with the test directory value. Generates this test server config file and places it in a temp location.mcp-server-testervianpx.Example run:
To run the tests for
local-operationssimply run./run_tests.sh local-operationsUpdate snapshot format - @DaleSeo PR #313
Updates all inline snapshots in the codebase to ensure they are consistent with the latest insta format.
Hardcoded version strings in tests - @DaleSeo PR #305
The GraphQL tests have hardcoded version strings that we need to update manually each time we release a new version. Since this isn't included in the release checklist, it's easy to miss it and only notice the test failures later.