[@sentry/angular] Update Angular to v21

[gordeevladislav]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/angular

SDK Version

10.26.0

Framework Version

Angular 21.0.0

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

Run npm i @sentry/angular in any Angular v21 project.

Expected Result

found 0 vulnerabilities

Actual Result

npm error Found: @angular/common@21.0.0
npm error node_modules/@angular/common
npm error @angular/common@"^21.0.0" from the root project
npm error peer @angular/common@"^21.0.0 || ^22.0.0" from @angular/cdk@21.0.0
npm error node_modules/@angular/cdk
npm error @angular/cdk@"^21.0.0" from the root project
npm error 40 more (@angular/forms, @angular/platform-browser, ...)
npm error
npm error Could not resolve dependency:
npm error peer @angular/common@">= 14.x <= 20.x" from @sentry/angular@10.26.0
npm error node_modules/@sentry/angular
npm error @sentry/angular@"^10.26.0" from the root project
npm error
npm error Conflicting peer dependency: @angular/common@20.3.13
npm error node_modules/@angular/common
npm error peer @angular/common@">= 14.x <= 20.x" from @sentry/angular@10.26.0
npm error node_modules/@sentry/angular
npm error @sentry/angular@"^10.26.0" from the root project
npm error

Additional Context

No response

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1206

[Lms24]

Hi, thanks for writing in! I'm surprised that this time the issue took so long to be opened 😅

I'm fully aware and already merged #18274 which should bump peer dependencies accordingly. The change will be included with the next release but because of an unrelated issue, we have to wait just a little bit longer with publishing. Probably end of day today or tomorrow. Sorry for the inconvenience!

Usually we close issues with already merged PRs but I'll keep this open since I can see a lot of people running into it.

In the meantime, you can do a forced install (not ideal, I know). According to the new Angular 21 e2e test app I added in the PR, things should work just fine!