Repository navigation
chore(deps): refresh dependencies and keep updates manageable - #117
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.
Summary
Refresh the backed-up app dependencies against current main and keep CodeQL initialization and analysis on the same version. Reduce routine Dependabot PR volume and keep Node types aligned with the Node 22 build runtime.
Type of Change
Infrastructure/CI
Technical Details
chore(site)prefix and a separate website group.Testing Performed
git diff --checkpassed.c31134c769c8ce439ab4f38e30beb6f6e1abb61d.Breaking Changes
None. Existing application behavior and the Node 22 build runtime are retained.