feature(CI): Simplify test workflow to always use production API key - #1
Merged
Merged
Conversation
Drop the separate staging API key. Staging and preview runs use the production API key and additionally send Cloudflare Access credentials. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SF8uEam7rXgJWppNpEbr3v
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
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
Updated the test workflow to always use the production API key regardless of the target environment, while maintaining separate Cloudflare Access credentials for non-production deployments.
Key Changes
APERIODIC_API_KEYenvironment variable to always use the production secretImplementation Details
The change reflects a shift in credential management strategy where:
https://claude.ai/code/session_01SF8uEam7rXgJWppNpEbr3v