fix(ci): fall back to legacy LLM API key secret - #1026
Open
RerankerGuo wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Self-CI bootstrap note: run #1655 uses the |
This was referenced Jul 14, 2026
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
AGENTTEAMS_LLM_API_KEY.HICLAW_LLM_API_KEYwhile repository secrets are migrated.Root cause
The AgentTeams contract rename changed the workflow to read only
secrets.AGENTTEAMS_LLM_API_KEY, but the configured repository secret still uses the legacy name. Run #1647 therefore failed eight integration jobs before any test started withLLM API Key is required.Verification
.github/workflows/test-integration.ymlwith PyYAML.git diff --checkThis unblocks current PR CI, including #985, without exposing or renaming any secret.