Bump @angular/compiler from 14.2.2 to 15.0.1

[dependabot]

Bumps @angular/compiler from 14.2.2 to 15.0.1.

Release notes

Sourced from @​angular/compiler's releases.

v15.0.1

15.0.1 (2022-11-22)

common

Commit	Description
	Fix MockPlatformLocation events and missing onPopState implementation (#48113)

forms

Commit	Description
	don't mutate validators array (#47830)
	FormBuilder.group return right type with shorthand parameters. (#48084)

language-service

Commit	Description
	correctly handle host directive inputs/outputs (#48147)
	update packages/language-service/build.sh script to work with vscode-ng-language-service's new Bazel build (#48120)

router

Commit	Description
	correct type of nextState parameter in canDeactivate (#48038)
	Ensure renavigating in component init works with enabledBlocking (#48063)
	restore 'history.state' on popstate even if navigationId missing (#48033)

Special Thanks

Alan Agius, Andrew Scott, Bjarki, Bob Watson, Brooke, Derek Cormier, Dylan Hunn, George Kalpakas, Greg Magolan, Ikko Ashimine, Ivan Rodriguez, Jessica Janiuk, Joe Roxbury, Joey Perrott, Kristiyan Kostadinov, Matthieu Riegler, Mikhail Savchuk, Nebojsa Cvetkovic, Pawel Kozlowski, Volodymyr and Wooshaah

v15.0.0

15.0.0 (2022-11-16)

Breaking Changes

compiler

• Keyframes names are now prefixed with the component's "scope name". For example, the following keyframes rule in a component definition, whose "scope name" is host-my-cmp:

  @​keyframes foo { ... }

  will become:

  @​keyframes host-my-cmp_foo { ... }

  Any TypeScript/JavaScript code which relied on the names of keyframes rules will no longer match.

  The recommended solutions in this case are to either:

  • change the component's view encapsulation to the None or ShadowDom
  • define keyframes rules in global stylesheets (e.g styles.css)
  • define keyframes rules programmatically in code.

compiler-cli

• Invalid constructors for DI may now report compilation errors

... (truncated)

Changelog

Sourced from @​angular/compiler's changelog.

15.0.1 (2022-11-22)

common

Commit	Type	Description
930af9dd26	fix	Fix MockPlatformLocation events and missing onPopState implementation (#48113)

forms

Commit	Type	Description
b342e55509	fix	don't mutate validators array (#47830)
a12a120272	fix	FormBuilder.group return right type with shorthand parameters. (#48084)

language-service

Commit	Type	Description
cc8b76ef7c	fix	correctly handle host directive inputs/outputs (#48147)
a8c33bf931	fix	update packages/language-service/build.sh script to work with vscode-ng-language-service's new Bazel build (#48120)

router

Commit	Type	Description
e4309d57d8	fix	correct type of nextState parameter in canDeactivate (#48038)
9baefd085f	fix	Ensure renavigating in component init works with enabledBlocking (#48063)
fa5528fb5f	fix	restore 'history.state' on popstate even if navigationId missing (#48033)

Special Thanks

Alan Agius, Andrew Scott, Bjarki, Bob Watson, Brooke, Derek Cormier, Dylan Hunn, George Kalpakas, Greg Magolan, Ikko Ashimine, Ivan Rodriguez, Jessica Janiuk, Joe Roxbury, Joey Perrott, Kristiyan Kostadinov, Matthieu Riegler, Mikhail Savchuk, Nebojsa Cvetkovic, Pawel Kozlowski, Volodymyr and Wooshaah

15.1.0-next.0 (2022-11-22)

Deprecations

router

• router writable properties

  The following strategies are meant to be configured by registering the application strategy in DI via the providers in the root NgModule or bootstrapApplication:

  • routeReuseStrategy
  • titleStrategy
  • urlHandlingStrategy

  The following options are meant to be configured using the options available in RouterModule.forRoot or provideRouter.

  • onSameUrlNavigation
  • paramsInheritanceStrategy
  • urlUpdateStrategy
  • canceledNavigationResolution

  The following options are available in RouterModule.forRoot but not available in provideRouter:

  • malformedUriErrorHandler - This was found to not be used anywhere internally.

... (truncated)

Commits

• 4199a8d build(bazel): fix missing dgeni dependencies
• 500acfc build(bazel): create AIO example playgrounds for manual testing
• 8d24a91 build(bazel): refactor aio example e2es to fix windows performance
• a36034a build(bazel): stamp targets to build, test, and serve aio against
• 12855f3 build(bazel): incrementally run aio example e2e tests
• 28f289b fix(core): hardening attribute and property binding rules for <iframe> elemen...
• 173dde7 Revert "fix(core): hardening rules related to the attribute order on iframe e...
• d4b3c0b fix(core): hardening rules related to the attribute order on iframe elements ...
• 39b72e2 fix(compiler): update element schema (#47552)
• 1b9fd46 feat(core): add support for Node.js version 18 (#47730)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[k8s-ci-robot]

Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages.

The list of commits with invalid commit messages:

• 1debbec Bump @angular/compiler from 14.2.2 to 15.0.1

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-ci-robot]

Keywords which can automatically close issues and at(@) mentions are not allowed in the title of a Pull Request.

You can edit the title by writing /retitle in a comment.

When GitHub merges a Pull Request, the title is included in the merge commit. To avoid invalid keywords in the merge commit, please edit the title of the PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[netlify]

❌ Deploy Preview for kubernetes-sigs-release-notes failed.

Name	Link
🔨 Latest commit	1debbec
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-release-notes/deploys/637dfe935d33800008e0a287

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign saschagrunert for approval by writing /assign @saschagrunert in a comment. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

@dependabot[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-release-notes-e2e	1debbec	link	true	/test pull-release-notes-e2e
pull-release-notes-build-prod	1debbec	link	true	/test pull-release-notes-build-prod
pull-release-notes-build-dev	1debbec	link	true	/test pull-release-notes-build-dev

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[dependabot]

Superseded by #438.