ci: dispatch instanode-web auth-contract Playwright on api PR#204
Merged
Conversation
Cross-repo Layer-1 trigger. The api owns the CORS allowlist + /auth/exchange + /auth/email/start endpoints — an api-side change that drops access-control-allow-credentials wouldn't trigger instanode-web's CI on its own, so today's 2026-05-29 → 2026-05-30 login regression could ship despite green api unit tests. This job fires a repository_dispatch on instanode-web; it listens for 'auth-contract-e2e-from-api' and runs the Chromium smoke against prod (see instanode-web PR #153). Soft-skips if REPO_ACCESS_TOKEN secret is missing so api CI stays green during initial rollout. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Cross-repo Layer-1 trigger paired with instanode-web #153.
Why
The api owns the CORS allowlist +
/auth/exchange+/auth/email/start. An api-side change that dropsaccess-control-allow-credentialswouldn't trigger instanode-web's CI on its own, so today's regression could ship despite green api unit tests.What
New
dispatch-auth-contract-e2ejob inci.ymlthat firesrepository_dispatchon instanode-web (typeauth-contract-e2e-from-api). The web side already has the listener (PR #153).Safety
pull_requestorpushto master.env:(security-guidance compliant).REPO_ACCESS_TOKENsecret missing → api CI stays green during rollout.Coverage (rule 17)
ci.yml)