Conversation
This was referenced Sep 15, 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
EE_DB_*workflow-call names for compatibility.ci.yamlno longer consumes them.Root cause
MatrixOne's reusable-workflow call was rejected before runner allocation when the caller could not provide
EE_DB_ADDR,EE_DB_PORT,EE_DB_USER,EE_DB_PASSWORD, andEE_DB_DB. These declarations were added for the historical failed-UT-to-MOC action, which is no longer present in this workflow. The currentci.yamlhas nosecrets.EE_DB_*consumer.This is the shared-workflow side of matrixorigin/matrixone#27822. It also unblocks the ordered restoration of the four-shard race-UT caller described by the recurrence tracked in matrixorigin/matrixone#28538.
Compatibility and security
This is a monotonic contract relaxation: callers that pass these secrets behave exactly as before, while callers that do not pass unused credentials are no longer rejected at workflow evaluation. The names remain declared for explicit callers. No credential is added to a job environment or forwarded to a new consumer.
If an EE database is needed again, the workflow that actually consumes it must declare and validate that dependency locally.
Test plan
git diff --check.github/workflows/ci.yamlEE_DB_*declarations arerequired: falseci.yamlcontains nosecrets.EE_DB_*consumer