Update SECURITY.md - #17034
Closed
ox5qmuteb-dotcom wants to merge 1 commit into
Closed
Update SECURITY.md#17034ox5qmuteb-dotcom wants to merge 1 commit into
ox5qmuteb-dotcom wants to merge 1 commit into
Conversation
Member
|
Are you drunk? |
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
2 participants
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.
What changed and why
Describe what this PR changes and why the change is needed. Include the problem being solved and the approach taken.
How to test
Describe how to verify the changes work as expected. Include steps, commands, or scenarios.
Related issue(s)/PR(s)
Provide any issue addressed by this change using the format
Resolves #<number>. Mention other related issues or pull requests with relevant context.Compatibility notes
Describe any platform, environment, or integration considerations. State if the change is universal or scoped to specific configurations.
Breaking change assessment
Does this change any public API signature, return type, or default behavior? Is it safe for patch-level consumers? State explicitly.
Test coverage
List tests added or modified. If none, state why.
Contributors
Acknowledge by GitHub handle any contributor whose issue or prior work prompted this change.
AI tool use
If AI tools played a meaningful role in producing this contribution, describe what you used and how. See AI-POLICY.md for the project's full position. If AI tools were not involved, leave this section blank or remove it.