Repository navigation
ci: add daily security audits and fix PRs - #2368
Merged
Merged
Conversation
aeharding
enabled auto-merge (squash)
October 24, 2026 20:52
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.
Run security audits every 24 hours at 13:17 UTC, with a manual GitHub Actions trigger. Check the Node.js pin against official security-release/support metadata, scan supported dependency lockfiles including development dependencies, and scan the published application container plus every external Dockerfile base for OS/library vulnerabilities. Resolve source image references dynamically so digest pins are audited exactly. Summaries flag high/critical findings, including ones with no published fix, and retain complete reports for 30 days.
Run Renovate independently to prepare security-fix PRs and runtime/image patch updates using the existing release credential so normal CI is triggered. Keep Node updates within its current major; keep other runtimes on their patch release lines. Fix PRs require review and do not automatically merge or publish stable releases. GitHub vulnerability alerts are enabled; Renovate handles remediation to avoid duplicate Dependabot fix PRs.
Also update the known-vulnerable Node.js 26.8.2 pin to the patched 26.12.1 release, and make Docker builds pull fresh base images. The maintenance documentation describes coverage limits, including unresolved Android transitive dependencies and platform-managed WebViews.
Validation: the runtime audit passes against live official Node.js feeds; the exact Renovate 44.181.4 validator accepts the configuration; report checks verify clean/low-severity success, high/critical failures including unfixed findings, and failure on malformed scanner output. Inventory checks verify exact digest preservation, stage-alias exclusion, and failure on unresolved images. YAML/JavaScript/Python syntax, formatting, and git diff --check pass. Existing project CI validates the runtime change. The scheduled workflow will be manually exercised after merge to verify end-to-end scanning and fix PR creation.