Repository navigation
chore(deps): consolidate updates and group Dependabot PRs - #110
Merged
Merged
Conversation
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.
Consolidates the nine open Dependabot PRs into one update and configures Dependabot to open one weekly version-update PR covering npm, Cargo and GitHub Actions. Security updates remain independent of the weekly group. The group includes all version updates, including major releases, which still require review before merging.
Supersedes #90, #92, #93, #95, #96, #102, #104, #105 and #106.
Validation: 647 tests across 22 suites, ESLint, production web build, locked macOS cargo check, actionlint and Dependabot configuration schema validation passed locally. Cargo check also passes without a built frontend, matching the new CI job.
npm audit --omit=devreports zero vulnerabilities. Compatible fixes reduce high-severity findings from 14 on main to 5; the remaining high findings are the existing braces/gh-pages development-tool chain. npm's suggested force fix would downgrade tools and is outside this update. The security workflow retains its existing advisory-only behavior.