[Snyk] Security upgrade @angular-devkit/build-angular from 19.2.19 to 20.3.15

[Dustin4444]

Snyk has created this PR to fix 2 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

• integrations/angular-cli-19/package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Server-side Request Forgery (SSRF) SNYK-JS-WEBPACK-15235959	84
	Server-side Request Forgery (SSRF) SNYK-JS-WEBPACK-15235969	84

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Server-side Request Forgery (SSRF)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
v0-open-in-v0-0w	Error		Feb 8, 2026 3:28am

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-8f41ab17ff3fc0fc1d2bb18cfad912a8

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @Dustin4444, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates a critical security update for the project's development dependencies. By bumping the version of @angular-devkit/build-angular, it proactively mitigates identified security risks, specifically two Server-side Request Forgery vulnerabilities, thereby strengthening the project's overall security posture.

Highlights

• Dependency Upgrade: The @angular-devkit/build-angular dependency has been upgraded from version 19.2.19 to 20.3.15.
• Vulnerability Resolution: This upgrade addresses two low-severity Server-side Request Forgery (SSRF) vulnerabilities, SNYK-JS-WEBPACK-15235959 and SNYK-JS-WEBPACK-15235969.
• Manual Intervention Required: The pnpm-lock.yaml file failed to update automatically and requires manual resolution before merging.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• integrations/angular-cli-19/package.json
  • Updated @angular-devkit/build-angular in devDependencies from ^19.2.5 to ^20.3.15.

Activity

• The pull request was automatically generated by Snyk.
• Snyk identified and targeted two low-severity Server-side Request Forgery (SSRF) vulnerabilities for remediation.
• A warning was noted that the pnpm-lock.yaml file requires manual updating.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades @angular-devkit/build-angular to fix security vulnerabilities. However, this upgrade introduces a critical issue by creating a major version mismatch within the Angular dependencies. Upgrading @angular-devkit/build-angular to v20 while other packages like @angular/cli and @angular/core remain on v19 is very likely to break the build. The failure to update pnpm-lock.yaml noted in the description may be a symptom of this incompatibility. Before merging, it is crucial to update all @angular/* packages to a consistent major version to ensure the application remains stable and buildable.

[gemini-code-assist]

This upgrade introduces a major version mismatch between @angular-devkit/build-angular (v20) and other Angular packages in this project, such as @angular/cli (^19.2.5) and @angular/core (^19.2.4). Angular framework packages are designed to be used with the same major version. This inconsistency is highly likely to cause build failures or unexpected runtime errors. To resolve this, all @angular/* packages should be upgraded to the same major version (e.g., v20) to maintain a consistent and stable environment.