Repository navigation
CI upkeep: CodeQL init and analyze together; ci-minutes on short months - #177
Merged
Merged
Conversation
GitHub answers 0 runs, with no error, to a range ending on 11-31, so every month shorter than 31 days read as empty. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 4, 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.
Two small upkeep fixes.
CodeQL. Replaces #173 and #174.
initandanalyzemust run the same version, so each of those PRs fails theanalyzejob alone ("Loaded a configuration file for version '4.38.3', but running version '4.39.1'"). This bumps both to 4.39.1 and groupsgithub/codeql-action*independabot.ymlso the next bump arrives as one PR. The pinned SHA is the commit thev4.39.1tag points at, and it is the same one #176 already put onupload-sarif.scripts/ci-minutes.mjs. It asked forcreated=2026-11-01..2026-11-31. GitHub answers 0 runs to a range ending on a date that doesn't exist, with no error, so the meter printed "0 runs" for every month shorter than 31 days. Checked by calling the API:..11-31gives 0,..11-30gives 28, and..10-31gives 308 (the control: a real 31-day month was never affected). The fixed script now prints 28 runs and 40 billed minutes for November.No source or test changes.
🤖 Generated with Claude Code