Repository navigation
docs: drop stale CORS entry from the TEST known-issues list - #646
Closed
kcramakrishna wants to merge 1 commit into
Closed
kcramakrishna wants to merge 1 commit into
kcramakrishna wants to merge 1 commit into
Conversation
The TEST backend accepts browser origins since the F9 fix; the sanity job probes it on every deploy. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Member
Author
|
Folded into #648 so CI and the merge queue run once. |
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.
The TEST release notes list this file as known issues. The CORS rejection was fixed (F9); the TEST sanity job and PROD smoke now assert browser-origin responses on every deploy.
Replaces the entry with a 'none known' line.
🤖 Generated with Claude Code