Skip to content

test(angular): Add Angular 20.0.0-rc.2 e2e test #16364

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 6 commits into
base: develop
Choose a base branch
from

Conversation

Lms24
Copy link
Member

@Lms24 Lms24 commented May 22, 2025

This PR adds an e2e test for Angular the latest Angular 20 RC. Local testing so far confirms that the SDK works as expected. Let's see if CI is happy as well.

A nice overview of the changes so far in 20: https://www.angular.courses/caniuse?from=19&to=20&hasStatusChange=true

closes #16366

@Lms24 Lms24 self-assigned this May 22, 2025
@Lms24 Lms24 force-pushed the lms/test-e2e-angular-20 branch from 6896251 to c5184df Compare May 22, 2025 15:55
@Lms24 Lms24 requested review from a team, mydea, chargome and andreiborza and removed request for a team and mydea May 22, 2025 15:55
"@angular/animations": "^20.0.0-rc.2",
"@angular/common": "^20.0.0-rc.2",
"@angular/compiler": "^20.0.0-rc.2",
"@angular/core": "^20.0.0-rc.2",
Copy link
Member

Choose a reason for hiding this comment

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

wdyt about generally adding canary tests here with "@angular/<package>": "next"?

Copy link
Member Author

Choose a reason for hiding this comment

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

we could! Let me take a look how easy this would be. My only concern is that sometimes, it's not just the package versions that need updating but also the app config/module files. But I guess we'd probably see this in the canary tests. Will open a separate PR for canary tests though, as I wanna convert this application to 20 stable when it's released.

Copy link
Member

Choose a reason for hiding this comment

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

we can use the same format we use for other tests to run this for actual canary, the "normal" tests should not use canary as that may fail and we do not want to block on this!

package.json Outdated
@@ -44,7 +44,7 @@
"yalc:publish": "lerna run yalc:publish"
},
"volta": {
"node": "20.18.2",
"node": "20.19.0",
Copy link
Member

Choose a reason for hiding this comment

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

let's maybe pull this into a dedicated PR 🤔 wdyt?

Copy link
Member Author

Choose a reason for hiding this comment

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

yeah, good point. Still sucks that RR blocks Angular though, I'll try if I can somehow bypass the Node version check in Angular until we figured it out

Opened #16378 for the Node bump

@@ -886,7 +886,13 @@ jobs:
- uses: pnpm/action-setup@v4
with:
version: 9.4.0
- name: Set up Node for Angular 20
Copy link
Member Author

Choose a reason for hiding this comment

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

This is not ideal because we should use the same Node version to build the SDK and to build && run the app. But since we're blocked on upgrading to 20.19.0, I think this is a fair compromise for now.

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.

Create Angular 20RC e2e test app
4 participants