Skip to content

chore(deps): update lock files to resolve security alerts #31616

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thetaPC merged 5 commits into from
Oct 30, 2026
Merged

chore(deps): update lock files to resolve security alerts #31616

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ac0dfc7
chore(angular): type the outlet contexts access for Angular 22.2
thetaPC Oct 20, 2026
8befc3b
chore(deps): update lock files to resolve security alerts
thetaPC Oct 20, 2026
7dd31ac
chore(deps): override serve
thetaPC Oct 20, 2026
3f9d356
chore(angular): note checking the outlet contexts field on Angular up…
thetaPC Oct 30, 2026
de930f4
chore(deps): update picomatch, semver and vite in lock files
thetaPC Oct 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
898 changes: 435 additions & 463 deletions core/package-lock.json
View file
Open in desktop

@brandyscarney brandyscarney Oct 22, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

npm audit --package-lock-only still shows high alerts for picomatch 2.3.1 (core, react, vue), semver 6.3.0/7.3.7/5.7.1 (core), micromatch (core, react) and vite 7.3.6 (migrate). These look fixable within the current ranges, and the angular lock file already has picomatch 2.3.2. Could you refresh these, or call them out under Other information if they're being left on purpose?

@thetaPC thetaPC Oct 30, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Refreshed in de930f4. The update was based on open Dependabot alerts, and Dependabot had auto-dismissed the picomatch and semver ones as dev-scoped, so they never showed up. The vite advisory in migrate was published the day the update ran. vite is pinned to 7.3.7 since a plain npm update jumps to vite 8. npm audit --package-lock-only now only reports the postcss 7 from stylelint 13, which is already called out under Other information.

Large diffs are not rendered by default.

3 changes: 3 additions & 0 deletions core/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,6 +116,9 @@
"@typescript-eslint/parser": "$@typescript-eslint/parser",
"@typescript-eslint/eslint-plugin": "$@typescript-eslint/eslint-plugin",
"eslint-plugin-import": "$eslint-plugin-import"
},
"serve": {
"compression": "^1.8.2"
}
},
"scripts": {
Expand Down
6 changes: 3 additions & 3 deletions packages/angular-server/package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading
Loading