Skip to content

build: update to Angular 14 stable #25027

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

Merged
merged 1 commit into from
Jun 9, 2022
Merged

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Jun 5, 2022

Bumps up the repo to the stable version of Angular 14.

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: patch This PR is targeted for the next patch release labels Jun 5, 2022
@crisbeto crisbeto requested review from a team, andrewseguin and devversion as code owners June 5, 2022 08:29
crisbeto added a commit to crisbeto/angular that referenced this pull request Jun 5, 2022
`@angular/bazel` currently uses an older version of `@microsoft/api-extractor` which is causing downstream issues in Components. These changes bump up to a version that has a fix.

Context: angular/components#25027
@crisbeto
Copy link
Member Author

crisbeto commented Jun 5, 2022

Blocked until angular/angular#46259 is released.

@crisbeto crisbeto added the blocked This issue is blocked by some external factor, such as a prerequisite PR label Jun 5, 2022
alxhub pushed a commit to angular/angular that referenced this pull request Jun 6, 2022
`@angular/bazel` currently uses an older version of `@microsoft/api-extractor` which is causing downstream issues in Components. These changes bump up to a version that has a fix.

Context: angular/components#25027

PR Close #46259
alxhub pushed a commit to angular/angular that referenced this pull request Jun 6, 2022
`@angular/bazel` currently uses an older version of `@microsoft/api-extractor` which is causing downstream issues in Components. These changes bump up to a version that has a fix.

Context: angular/components#25027

PR Close #46259
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -72,7 +72,7 @@ function addAnimationsModule(options: Schema) {
try {
addAnimationsModuleToNonStandaloneApp(host, project, context, options);
} catch (e) {
if (e instanceof SchematicsException && e.message.includes('Bootstrap call not found')) {
if (e instanceof Error && e.message.includes('Bootstrap call not found')) {
Copy link
Member Author

Choose a reason for hiding this comment

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

I made this change, because I ended up with a version mismatch between some of the Tooling packages by accident which broke the check here. Checking against Error instead should be more robust.

Copy link
Member

Choose a reason for hiding this comment

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

FWIW: Amy and I had a similar issue last time where even instanceof Error did not work due to the devkit executing schematics in a different VM context. Might not be an issue here since it throws in the same VM context, but worth mentioning.. not ideal

Bumps up the repo to the stable version of Angular 14.
@crisbeto crisbeto added action: merge The PR is ready for merge by the caretaker and removed blocked This issue is blocked by some external factor, such as a prerequisite PR labels Jun 9, 2022
@crisbeto crisbeto merged commit 13d257c into angular:main Jun 9, 2022
crisbeto added a commit that referenced this pull request Jun 9, 2022
Bumps up the repo to the stable version of Angular 14.

(cherry picked from commit 13d257c)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jul 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants