[Snyk] Security upgrade @angular/cli from 19.2.22 to 20.3.15

[Dustin4444]

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

Snyk changed the following file(s):

• examples/angular/router/package.json

⚠️ Warning

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

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Directory Traversal SNYK-JS-TAR-15307072

---

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:

🦉 Directory Traversal

[gemini-code-assist]

Summary of Changes

Hello, 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 upgrade for the @angular/cli dependency within the examples/angular/router project. The primary goal is to mitigate a high-severity Directory Traversal vulnerability. Reviewers should note that the pnpm-lock.yaml file needs to be updated manually to reflect these changes.

Highlights

• Security Upgrade: Upgraded the @angular/cli dependency from 19.2.22 to 20.3.15 to address a security vulnerability.
• Vulnerability Fixed: Resolved a high-severity Directory Traversal vulnerability (SNYK-JS-TAR-15307072) related to the tar package.
• Manual Action Required: The pnpm-lock.yaml file was not automatically updated and requires manual intervention 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

• examples/angular/router/package.json
  • Updated @angular/cli dependency to version 20.3.15.

Activity

• Snyk automatically generated this pull request to address a security vulnerability.
• The PR targets a single high-severity vulnerability.
• A warning was provided indicating that the pnpm-lock.yaml file failed to update and requires manual attention.
• Snyk included links to a detailed project report, PR template customization, project settings, and documentation on its upgrade logic.
• An interactive lesson on Directory Traversal was also linked for educational purposes.

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. ↩

[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.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8869094a-16d3-4c1d-a153-de0a448541a7

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

Use the checkbox below for a quick retry:

• 🔍 Trigger 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-a3e279d8852961b397e1230dd240476e

---

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]

Code Review

This PR from Snyk updates @angular/cli to address a security vulnerability. The change itself is a good start, but there are two important points to consider before merging:

1. Incomplete Angular package updates: The PR only updates @angular/cli. It is a strong convention in Angular development to keep all @angular/* packages at the same version to ensure compatibility. I've left a specific suggestion to update @angular/build and @angular/compiler-cli as well.
2. Lockfile update required: As noted in the PR description, the pnpm-lock.yaml file has not been updated. This is a required step to ensure the vulnerability is actually fixed. After applying the suggested code changes, you must run pnpm install to update the lockfile and commit the result to this branch before merging.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

For consistency and to avoid potential compatibility issues, it's best practice to keep all @angular/* packages at the same version. Since @angular/cli is being updated to ^20.3.15, @angular/build and @angular/compiler-cli should also be updated to match this version.

Suggested change

	"@angular/build": "^20.0.0",
	"@angular/cli": "^20.0.0",
	"@angular/cli": "^20.3.15",
	"@angular/compiler-cli": "^20.0.0",
	"@angular/build": "^20.3.15",
	"@angular/cli": "^20.3.15",
	"@angular/compiler-cli": "^20.3.15",