docs(stop): Update stopping instructions and API note #44
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.
TL;DR
Updated documentation to remove the "coming soon" notice for stopping App invocations via the API, as this feature is no longer planned. Also updated deployment-listing code samples to use new pagination helpers.
Why we made these changes
The documentation for stopping invocations incorrectly suggested an API endpoint was "coming soon." This is no longer planned, so we're removing it to avoid user confusion. The code samples for listing deployments were also updated to reflect the latest, more ergonomic pagination methods in our client libraries.
What changed?
apps/stop.mdx: Removed the "Via API" section that described the feature as "coming soon."snippets/openapi/get-deployments.mdx: Updated Node.js and Python code examples to demonstrate new pagination handling (async iterables and page objects).Description generated by Mesa. Update settings