ci(build-system-tests): replace Angular 19 mega-app with Angular 20 - #7071
Merged
Conversation
Angular 19 is EOL as of 2026-05-19 and cannot satisfy the >= 20.0.0 peer range that @aws-amplify/ui-angular declares, which broke the publish-next canary build.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of changes
The
publish-nextworkflow has been failing on every push tomainsince the Angular 20 upgrade (#7047) landed. Thepublishjob itself succeeds, but the post-publish canary jobbuild-test / build (angular, 19, angular-cli, 19, npm, 24)fails duringnpm install:#7047 raised the
@aws-amplify/ui-angularpeer range to>= 20.0.0, but the build-system-test matrix still scaffolds an Angular 19 mega-app, so the published@nextpackage can no longer be installed there.install-with-retriesburns all 4 attempts and the job fails.This replaces the Angular 19 matrix entry with Angular 20. Angular 19 reached end of life on 2026-05-19, so there is no reason to keep it in the canary matrix. Pinning to 20 keeps coverage of the floor of the declared peer range, alongside the existing
latest(v22) entry.No script changes are needed: both
mega-app-copy-files.shandmega-app-install.shbranch on>= 21for the newer bootstrap config and the explicitzone.jsdependency, so an Angular 20 app takes the same path Angular 19 did.Issue #, if available
N/A
Description of how you validated changes
publish-nextfailures, all failing on the same Angular 19 job. The last greenpublish-nextrun predates chore(angular): upgrade @aws-amplify/ui-angular to Angular 20 #7047..github/workflows/reusable-build-system-test.ymlis the only place the Angular matrix is defined (build-system-test.ymldelegates to it, and the react-native reusable workflow has no Angular entries).latest+20with no remaining19entries.prettier --checkpasses on the modified file.angular-20-angular-cli-20mega-app runs on merge tomain.Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.