ci: fix CodeQL stale-config error and move workflow actions to Node 24#105
Merged
Conversation
Default CodeQL setup previously analyzed python, actions, and javascript-typescript. Switching to a Python-only custom workflow left the actions and javascript-typescript configurations stale, which GitHub surfaces as a "Code scanning configuration error" on the security page. - Add a language matrix covering python and actions so the actions configuration is refreshed on every run (and the workflow files themselves get security scanning). Use build-mode: none for both interpreted targets, dropping the now-unnecessary autobuild step. - The stale javascript-typescript analyses (the repo has no JS/TS source) were deleted out of band via the code-scanning API. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
CI emitted "Node.js 20 actions are deprecated" warnings. Bump the actions still running on Node 20 to their Node 24 releases: - github/codeql-action v3.32.6 -> v4.36.2 (init/analyze in codeql.yml, upload-sarif in scorecard.yml) - cycjimmy/semantic-release-action v4.2.2 -> v5.0.2 in release.yml; v5's only breaking change is the Node 24 runner (no semantic-release version bump), so it is a drop-in for the existing extra_plugins config. All other pinned actions already run on Node 24 (checkout v6, setup-python v6, setup-uv v8, setup-node v6, upload-artifact v7) or are composite/docker actions (quarto-actions, pypi-publish, scorecard-action). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
bartzbeielstein
changed the title
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.
Two related CI/security-workflow fixes.
1. Code scanning "configuration error"
CodeQL default setup previously analyzed three auto-detected languages —
python,actions, andjavascript-typescript(last run 2026-03-15). Commit25de631switched to a custom Python-only workflow, leaving theactionsandjavascript-typescriptconfigurations stale (previously reported results, no longer updated) — which GitHub flags as a configuration error.actions—codeql.ymlnow uses a language matrix analyzing bothpythonandactions, so that configuration is refreshed on every run (and the workflow files get security scanning).build-mode: nonefor both interpreted targets; the oldautobuildstep is dropped. Self-heals after merge tomain.javascript-typescript— the repo has zero tracked JS/TS source, so this config can't be refreshed. Its 147 stale analyses were deleted out of band via the code-scanning API.2. "Node.js 20 actions are deprecated"
Bumped the two actions still on the Node 20 runtime to their Node 24 releases:
github/codeql-actionv3.32.6 → v4.36.2 (init/analyzeincodeql.yml,upload-sarifinscorecard.yml)cycjimmy/semantic-release-actionv4.2.2 → v5.0.2 inrelease.yml— v5's only breaking change is the Node 24 runner (no bundled semantic-release version bump), so it's a drop-in for the existingextra_pluginsconfig. (v6 additionally jumps to semantic-release v25; deliberately not taken here to keep the release pipeline stable.)All other pinned actions already run on Node 24 (checkout v6, setup-python v6, setup-uv v8, setup-node v6, upload-artifact v7) or are composite/docker actions (quarto-actions, pypi-publish, scorecard-action). Actions remain pinned to full commit SHAs.
🤖 Generated with Claude Code