Skip to content

ci(sast): stop skipping CodeQL on release commits #220

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
timoa wants to merge 2 commits into
base: main
Choose a base branch
from
Open

ci(sast): stop skipping CodeQL on release commits #220

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ab4f151
ci(sast): stop skipping CodeQL on release commits
claude Aug 12, 2026
6feb296
Merge branch 'main' into agent/security-engineer/672fb509
timoa Aug 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion .releaserc.cjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,11 @@ module.exports = {
'@semantic-release/git',
{
assets: ['package.json', 'CHANGELOG.md'],
message: 'chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}',
// Intentional: no `[skip ci]` suffix. The release commit must
// trigger CodeQL so SAST scoring covers it (refs TIM-122 —
// SAST score 24/27). Release-only changes touch CHANGELOG.md
// and the package.json version bump, both cheap for CodeQL.
message: 'chore(release): ${nextRelease.version}\n\n${nextRelease.notes}',
},
],
[
Expand Down