Repository navigation
chore: Run nightly security audit at 1am Eastern - #430
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The nightly audit cron was
0 6 * * *UTC, which is 2am during EDT. GitHub also delays top-of-the-hour schedules heavily (the 2026-10-03 run started 5h18m late), so failures were landing mid-morning.17 1 * * *withtimezone: America/New_York(DST-aware, off the top of the hour)workflow_dispatchso the audit can be triggered on demand / by an external schedulerVerified the YAML diff by hand; the schedule only takes effect once merged to the default branch.
🤖 Generated with Claude Code