Repository navigation
Require security checks before documentation deployment - #125
Merged
Merged
Conversation
leemour
force-pushed
the
chore/security-deployment-gate
branch
from
October 10, 2026 20:17
ec60ecb to
db6d2ab
Compare
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.
Require the shared release security checks before production documentation deployment, preserving the existing build/browser policy. Confirmed critical production advisories, critical source findings, credential leaks and scanner failures stop deployment; other findings remain for owner review. The Next.js patch and fast PR/on-demand security checks are already merged in PR124.
The unchanged search-playground test previously clicked the server-rendered footer before its theme listener initialized. Wait for the initialized action label before clicking, retaining both theme and accessibility assertions. Targeted light/dark accessibility cases pass locally; lint and type checking pass. Unit tests pass after the required tool-source sync.
Rebased on current main aefe586. Shared release workflow has already passed hosted execution. Await current PR CI before merging; the previously reported credential limitation will be rechecked against this reviewed head.