Remove macos-13 from codeql workflow - #3274
Merged
mbg merged 1 commit intoNov 5, 2025
Merged
mbg merged 1 commit into
mbg merged 1 commit into
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 removes the macos-13 runner from the test matrix in the CodeQL workflow, reducing the macOS testing platforms from three versions (13, 14, 15) to two (14, 15).
- Removed macos-13 from the OS matrix in the analyze-javascript job
Sorry, something went wrong.
esbena
approved these changes
Nov 5, 2025
This was referenced Nov 13, 2025
This was referenced Nov 6, 2026
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.
Removes macos-13 from the codeql workflow. macos-13 runners will be removed by 4 December and brownouts have started for them, which are now causing this workflow to fail.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
CI only.
How did/will you validate this change?
CI
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
CI failures.
Merge / deployment checklist