Add canary tests for v2 API endpoints and triggers#1611
Merged
Conversation
Cover v2 resource commands, raw HTTP verbs to /v2/ paths, and v2 trigger fixtures to ensure the CLI correctly handles JSON content-type requests in production builds. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Committed-By-Agent: claude
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
2 participants
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.
Summary
v2 APIs have their own request shape, so we should cover them in the canary. This will ensure changes to auth don't break these flows unexpectedly.
Tested by triggering the workflow manually and seeing the requests succeed: https://github.com/stripe/stripe-cli/actions/runs/26467782853