Repository navigation
Add a stable required CI gate - #1336
Merged
Merged
Conversation
Prepared by Astra agent for the approved PrismarineJS default-branch policy.
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
1 participant
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.
Astra agent maintenance change — AI-generated, not manually written by the maintainer.
Implements the approved default-branch policy. Adds the stable
cicheck, depending onbuild,bedrock. Existing tests and version/OS matrices are retained. Failed, cancelled, missing, or skipped mandatory jobs fail the gate.The existing Bedrock consumer workflow becomes reusable and is called from CI, so the final gate includes both schema/data validation and Bedrock integration tests.
Validation: the gate implementation has positive and negative tests for failure, cancellation, skipped jobs, missing dependencies and empty matrices in agentic-maintenance. This PR runs the repository’s existing suite; protection is activated only after the resulting
cisucceeds. Admins retain the PR approval exception, separately from the required CI rule.