Skip to content

docs: update to Angular 19 #4762

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.

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

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

alex-okrushko
Copy link
Member

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

Most of it was automated migration

  • Update to latest Angular 19
  • Update angular/fire to 19 as well (they are now version-matching)
  • disable Polaris as it's causing issues (trying to get the non-existent dependency)
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Closes #

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Copy link

netlify bot commented Apr 21, 2025

Deploy Preview for ngrx-io failed.

Name Link
🔨 Latest commit fc46c4a
🔍 Latest deploy log https://app.netlify.com/sites/ngrx-io/deploys/6806b2e23534c80008ac56dd

Copy link
Member

@timdeschryver timdeschryver left a comment

Choose a reason for hiding this comment

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

@alex-okrushko Since we recently have a PR open to update the docs site (#4764) I wonder if we can close this PR. What's your opinion on this, do you think it's still useful?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants