-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
base: develop
Are you sure you want to change the base?
Conversation
6896251
to
c5184df
Compare
"@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", |
There was a problem hiding this comment.
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"
?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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", |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
.github/workflows/build.yml
Outdated
@@ -886,7 +886,13 @@ jobs: | |||
- uses: pnpm/action-setup@v4 | |||
with: | |||
version: 9.4.0 | |||
- name: Set up Node for Angular 20 |
There was a problem hiding this comment.
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.
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