Repository navigation
👷 ci(codeql): move to advanced setup on ubuntu-26.04 - #44
Closed
gaborbernat wants to merge 1 commit into
Closed
gaborbernat wants to merge 1 commit into
gaborbernat wants to merge 1 commit into
Conversation
Default setup runs on ubuntu-latest, which now warns that the label will migrate to Ubuntu 26. A committed workflow pins ubuntu-26.04 like the other jobs and keeps the same language, query suite and triggers.
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.
CodeQL default setup runs on
ubuntu-latest, so every scan shows a notice that the label will migrate to Ubuntu 26. This moves the scan to advanced setup with a committed workflow pinned toubuntu-26.04, matching the other jobs here, and the notice goes away.The workflow reproduces what default setup runs today: the
actionslanguage, thedefaultquery suite, and scans on pushes tomain, pull requests, a weekly schedule, plus manual dispatch. The workflow grants no permissions at the top level, and the job gets onlycontents: readandsecurity-events: write. Extra queries or configuration can follow separately.Rollout