ref(issues): Remove the query-injection settings gate - #126332
Draft
roggenkemper wants to merge 2 commits into
Draft
roggenkemper wants to merge 2 commits into
roggenkemper wants to merge 2 commits into
Conversation
github-actions
Bot
added
the
Scope: Frontend
This branch was successfully deployed
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.
Show the SQL injection query-value-length threshold without checking the issue visibility flag. The flag is already enabled for every organization, so this preserves the released settings behavior when the flag is retired.
The regression test renders settings without the flag and checks the configured slider value; it fails with the existing gate. Deploy this frontend change before removing the flag's YAML entry or registration.