Add changelog entry for post-processing change - #3234
Merged
mbg merged 1 commit intoOct 24, 2025
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds a changelog entry documenting a behavioral change in the CodeQL Action's post-processing of SARIF files. The change ensures that post-processing steps are always performed regardless of upload settings, which may affect Advanced Setup users who use non-default upload input values.
- Adds a changelog entry for PR #3222 that modifies SARIF post-processing behavior
Sorry, something went wrong.
henrymercer
approved these changes
Oct 24, 2025
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
Reviewers
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.
Adds a changelog entry for #3222
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
N/A
How did/will you validate this change?
N/A
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
N/A
How will you know if something goes wrong after this change is released?
N/A
Merge / deployment checklist