chore(deps): bump the angular-all-deps group in /test/angular with 11 updates #184

dependabot · 2024-03-26T11:18:13Z

Bumps the angular-all-deps group in /test/angular with 11 updates:

Package	From	To
@angular/animations	`17.3.0`	`17.3.1`
@angular/common	`17.3.0`	`17.3.1`
@angular/compiler	`17.3.0`	`17.3.1`
@angular/core	`17.3.0`	`17.3.1`
@angular/forms	`17.3.0`	`17.3.1`
@angular/platform-browser	`17.3.0`	`17.3.1`
@angular/platform-browser-dynamic	`17.3.0`	`17.3.1`
@angular/router	`17.3.0`	`17.3.1`
@angular-devkit/build-angular	`17.3.0`	`17.3.2`
@angular/cli	`17.3.0`	`17.3.2`
@angular/compiler-cli	`17.3.0`	`17.3.1`

Updates @angular/animations from 17.3.0 to 17.3.1

Release notes

Sourced from @angular/animations's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit Description

capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Description

symbol feature detection for the compiler (#54711)

Changelog

Sourced from @angular/animations's changelog.

17.3.1 (2024-03-20)

compiler

Commit Type Description

c0788200e2 fix capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Type Description

99e9474aa2 fix symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.

The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.

When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check after one round completes. In rare cases, this can result in infinite loops when certain patterns continue to mark views for check using ChangeDetectorRef.detectChanges. This will be surfaced as a runtime error with the NG0103 code.

The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely matches the behavior of how a component would refresh in production. The order of component refresh in tests may be slightly affected as a result, especially when dealing with additional components attached to the application, such as dialogs. Tests sensitive to this type of change (such as screenshot tests) may need to be updated. Concretely, this change means that the component will refresh before additional views attached to ApplicationRef (i.e. dialog components). Prior to this change, the fixture component would refresh after other views attached to the application.

The exact timing of change detection execution when using event or run coalescing with NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.

Newly created and views marked for check and reattached

... (truncated)

Commits

See full diff in compare view

Updates @angular/common from 17.3.0 to 17.3.1

Release notes

Sourced from @angular/common's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit Description

capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Description

symbol feature detection for the compiler (#54711)

Changelog

Sourced from @angular/common's changelog.

17.3.1 (2024-03-20)

compiler

Commit Type Description

c0788200e2 fix capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Type Description

99e9474aa2 fix symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.

The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.

When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check after one round completes. In rare cases, this can result in infinite loops when certain patterns continue to mark views for check using ChangeDetectorRef.detectChanges. This will be surfaced as a runtime error with the NG0103 code.

The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely matches the behavior of how a component would refresh in production. The order of component refresh in tests may be slightly affected as a result, especially when dealing with additional components attached to the application, such as dialogs. Tests sensitive to this type of change (such as screenshot tests) may need to be updated. Concretely, this change means that the component will refresh before additional views attached to ApplicationRef (i.e. dialog components). Prior to this change, the fixture component would refresh after other views attached to the application.

The exact timing of change detection execution when using event or run coalescing with NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.

Newly created and views marked for check and reattached

... (truncated)

Commits

See full diff in compare view

Updates @angular/compiler from 17.3.0 to 17.3.1

Release notes

Sourced from @angular/compiler's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit Description

capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Description

symbol feature detection for the compiler (#54711)

Changelog

Sourced from @angular/compiler's changelog.

17.3.1 (2024-03-20)

compiler

Commit Type Description

c0788200e2 fix capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Type Description

99e9474aa2 fix symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.

The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.

When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check after one round completes. In rare cases, this can result in infinite loops when certain patterns continue to mark views for check using ChangeDetectorRef.detectChanges. This will be surfaced as a runtime error with the NG0103 code.

The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely matches the behavior of how a component would refresh in production. The order of component refresh in tests may be slightly affected as a result, especially when dealing with additional components attached to the application, such as dialogs. Tests sensitive to this type of change (such as screenshot tests) may need to be updated. Concretely, this change means that the component will refresh before additional views attached to ApplicationRef (i.e. dialog components). Prior to this change, the fixture component would refresh after other views attached to the application.

The exact timing of change detection execution when using event or run coalescing with NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.

Newly created and views marked for check and reattached

... (truncated)

Commits

c078820 fix(compiler): capture data bindings for content projection purposes in block...
See full diff in compare view

Updates @angular/core from 17.3.0 to 17.3.1

Release notes

Sourced from @angular/core's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit Description

capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Description

symbol feature detection for the compiler (#54711)

Changelog

Sourced from @angular/core's changelog.

17.3.1 (2024-03-20)

compiler

Commit Type Description

c0788200e2 fix capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Type Description

99e9474aa2 fix symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.

The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.

When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check after one round completes. In rare cases, this can result in infinite loops when certain patterns continue to mark views for check using ChangeDetectorRef.detectChanges. This will be surfaced as a runtime error with the NG0103 code.

The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely matches the behavior of how a component would refresh in production. The order of component refresh in tests may be slightly affected as a result, especially when dealing with additional components attached to the application, such as dialogs. Tests sensitive to this type of change (such as screenshot tests) may need to be updated. Concretely, this change means that the component will refresh before additional views attached to ApplicationRef (i.e. dialog components). Prior to this change, the fixture component would refresh after other views attached to the application.

The exact timing of change detection execution when using event or run coalescing with NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.

Newly created and views marked for check and reattached

... (truncated)

Commits

e70228a refactor(core): Add hydration missmatch on the component rather than the node...
1f5ab96 refactor(core): allow passing an environment injector while creating a view (...
c078820 fix(compiler): capture data bindings for content projection purposes in block...
See full diff in compare view

Updates @angular/forms from 17.3.0 to 17.3.1

Release notes

Sourced from @angular/forms's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit Description

capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Description

symbol feature detection for the compiler (#54711)

Changelog

Sourced from @angular/forms's changelog.

17.3.1 (2024-03-20)

compiler

Commit Type Description

c0788200e2 fix capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Type Description

99e9474aa2 fix symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.

The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.

When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check after one round completes. In rare cases, this can result in infinite loops when certain patterns continue to mark views for check using ChangeDetectorRef.detectChanges. This will be surfaced as a runtime error with the NG0103 code.

The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely matches the behavior of how a component would refresh in production. The order of component refresh in tests may be slightly affected as a result, especially when dealing with additional components attached to the application, such as dialogs. Tests sensitive to this type of change (such as screenshot tests) may need to be updated. Concretely, this change means that the component will refresh before additional views attached to ApplicationRef (i.e. dialog components). Prior to this change, the fixture component would refresh after other views attached to the application.

The exact timing of change detection execution when using event or run coalescing with NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.

Newly created and views marked for check and reattached

... (truncated)

Commits

See full diff in compare view

Updates @angular/platform-browser from 17.3.0 to 17.3.1

Release notes

Sourced from @angular/platform-browser's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit Description

capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Description

symbol feature detection for the compiler (#54711)

Changelog

Sourced from @angular/platform-browser's changelog.

17.3.1 (2024-03-20)

compiler

Commit Type Description

c0788200e2 fix capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Type Description

99e9474aa2 fix symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.

The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.

When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check after one round completes. In rare cases, this can result in infinite loops when certain patterns continue to mark views for check using ChangeDetectorRef.detectChanges. This will be surfaced as a runtime error with the NG0103 code.

The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely matches the behavior of how a component would refresh in production. The order of component refresh in tests may be slightly affected as a result, especially when dealing with additional components attached to the application, such as dialogs. Tests sensitive to this type of change (such as screenshot tests) may need to be updated. Concretely, this change means that the component will refresh before additional views attached to ApplicationRef (i.e. dialog components). Prior to this change, the fixture component would refresh after other views attached to the application.

The exact timing of change detection execution when using event or run coalescing with NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.

Newly created and views marked for check and reattached

... (truncated)

Commits

See full diff in compare view

Updates @angular/platform-browser-dynamic from 17.3.0 to 17.3.1

Release notes

Sourced from @angular/platform-browser-dynamic's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit Description

capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Description

symbol feature detection for the compiler (#54711)

Changelog

Sourced from @angular/platform-browser-dynamic's changelog.

17.3.1 (2024-03-20)

compiler

Commit Type Description

c0788200e2 fix capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Type Description

99e9474aa2 fix symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.

The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.

When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check after one round completes. In rare cases, this can result in infinite loops when certain patterns continue to mark views for check using ChangeDetectorRef.detectChanges. This will be surfaced as a runtime error with the NG0103 code.

The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely matches the behavior of how a component would refresh in production. The order of component refresh in tests may be slightly affected as a result, especially when dealing with additional components attached to the application, such as dialogs. Tests sensitive to this type of change (such as screenshot tests) may need to be updated. Concretely, this change means that the component will refresh before additional views attached to ApplicationRef (i.e. dialog components). Prior to this change, the fixture component would refresh after other views attached to the application.

The exact timing of change detection execution when using event or run coalescing with NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.

Newly created and views marked for check and reattached

... (truncated)

Commits

See full diff in compare view

Updates @angular/router from 17.3.0 to 17.3.1

Release notes

Sourced from @angular/router's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit Description

capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Description

symbol feature detection for the compiler (#54711)

Changelog

Sourced from @angular/router's changelog.

17.3.1 (2024-03-20)

compiler

Commit Type Description

c0788200e2 fix capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Type Description

99e9474aa2 fix symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.

The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.

When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check after one round completes. In rare cases, this can result in infinite loops when certain patterns continue to mark views for check using ChangeDetectorRef.detectChanges. This will be surfaced as a runtime error with the NG0103 code.

The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely matches the behavior of how a component would refresh in production. The order of component refresh in tests may be slightly affected as a result, especially when dealing with additional components attached to the application, such as dialogs. Tests sensitive to this type of change (such as screenshot tests) may need to be updated. Concretely, this change means that the component will refresh before additional views attached to ApplicationRef (i.e. dialog components). Prior to this change, the fixture component would refresh after other views attached to the application.

The exact timing of change detection execution when using event or run coalescing with NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.

Newly created and views marked for check and reattached

... (truncated)

Commits

See full diff in compare view

Updates @angular-devkit/build-angular from 17.3.0 to 17.3.2

Release notes

Sourced from @angular-devkit/build-angular's releases.

v17.3.2

17.3.2 (2024-03-25)

@schematics/angular

Commit Description

rename SSR port env variable

@angular-devkit/build-angular

Commit Description

Internal server error: Invalid URL when using a non localhost IP

ensure proper resolution of linked SCSS files

service-worker references non-existent named index output

update webpack-dev-middleware to 6.1.2

v17.3.1

17.3.1 (2024-03-20)

@schematics/angular

Commit Description

improve Sass format clarity for application style option

@angular-devkit/build-angular

Commit Description

only generate server directory when SSR is enabled

typo in allowedHosts warning for unsupported vite options

avoid transforming empty component stylesheets

reduce build times for apps with a large number of components when utilizing esbuild-based builders

Changelog

Sourced from @angular-devkit/build-angular's changelog.

17.3.2 (2024-03-25)

@schematics/angular

Commit Type Description

935f931ee fix rename SSR port env variable

@angular-devkit/build-angular

Commit Type Description

c9d436000 fix Internal server error: Invalid URL when using a non localhost IP

59fba38ec fix ensure proper resolution of linked SCSS files

27dd8f208 fix service-worker references non-existent named index output

c12907d92 fix update webpack-dev-middleware to 6.1.2

16.2.13 (2024-03-25)

@angular-devkit/build-angular

Commit Type Description

5ad507e3d fix update webpack-dev-middleware to 6.1.2

15.2.11 (2024-03-25)

@angular-devkit/build-angular

Commit Type Description

c6feb0bb0 fix update webpack-dev-middleware to 6.1.2

18.0.0-next.0 (2024-03-21)

Breaking Changes

@angular/cli

... (truncated)

Commits

8a6550d release: cut the v17.3.2 release
59fba38 fix(@angular-devkit/build-angular): ensure proper resolution of linked SCSS f...
27dd8f2 fix(@angular-devkit/build-angular): service-worker references non-existent na...
935f931 fix(@schematics/angular): rename SSR port env variable
c12907d fix(@angular-devkit/build-angular): update webpack-dev-middleware to 6.1.2
c9d4360 fix(@angular-devkit/build-angular): Internal server error: Invalid URL when...
1a3257a refactor(@schematics/angular): Use MaybeAsync and GuardResult types to reduce...
7041511 release: cut the v17.3.1 release
198ca9a fix(@schematics/angular): improve Sass format clarity for application style o...
2809971 fix(@angular-devkit/build-angular): only generate server directory when SSR...
Additional commits viewable in compare view

Updates @angular/cli from 17.3.0 to 17.3.2

Release notes

Sourced from @angular/cli's releases.

v17.3.2

17.3.2 (2024-03-25)

@schematics/angular

Commit Description

rename SSR port env variable

@angular-devkit/build-angular

Commit Description

Internal server error: Invalid URL when using a non localhost IP

ensure proper resolution of linked SCSS files

service-worker references non-existent named index output

update webpack-dev-middleware to 6.1.2

v17.3.1

17.3.1 (2024-03-20)

@schematics/angular

Commit Description

improve Sass format clarity for application style option

@angular-devkit/build-angular

Commit Description

only generate server directory when SSR is enabled

typo in allowedHosts warning for unsupported vite options

avoid transforming empty component stylesheets

reduce build times for apps with a large number of components when utilizing esbuild-based builders

Changelog

Sourced from @angular/cli's changelog.

17.3.2 (2024-03-25)

@schematics/angular

Commit Type Description

935f931ee fix rename SSR port env variable

@angular-devkit/build-angular

Commit Type Description

c9d436000 fix Internal server error: Invalid URL when using a non localhost IP

59fba38ec fix ensure proper resolution of linked SCSS files

27dd8f208 fix service-worker references non-existent named index output

c12907d92 fix update webpack-dev-middleware to 6.1.2

16.2.13 (2024-03-25)

@angular-devkit/build-angular

Commit Type Description

5ad507e3d fix update webpack-dev-middleware to 6.1.2

15.2.11 (2024-03-25)

@angular-devkit/build-angular

Commit Type Description

c6feb0bb0 fix update webpack-dev-middleware to 6.1.2

18.0.0-next.0 (2024-03-21)

Breaking Changes

@angular/cli

... (truncated)

Commits

8a6550d release: cut the v17.3.2 release
59fba38 fix(@angular-devkit/build-angular): ensure proper resolution of linked SCSS f...
27dd8f2 fix(@angular-devkit/build-angular): service-worker references non-existent na...
935f931 fix(@schematics/angular): rename SSR port env variable
c12907d fix(@angular-devkit/build-angular): update webpack-dev-middleware to 6.1.2
c9d4360 fix(@angular-devkit/build-angular): Internal server error: Invalid URL when...
1a3257a refactor(@schematics/angular): Use MaybeAsync and GuardResult types to reduce...
7041511 release: cut the v17.3.1 release
198ca9a fix(@schematics/angular): improve Sass format clarity for application style o...
2809971 fix(@angular-devkit/build-angular): only generate server directory when SSR...
Additional commits viewable in compare view

Updates @angular/compiler-cli from 17.3.0 to 17.3.1

Release notes

Sourced from @angular/compiler-cli's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit Description

capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Description

symbol feature detection for the compiler (#54711)

Changelog

Sourced from @angular/compiler-cli's changelog.

17.3.1 (2024-03-20)

compiler

Commit Type Description

c0788200e2 fix capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Type Description

99e9474aa2 fix symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.

The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be ...
Description has been truncated

netlify · 2024-03-26T11:18:30Z

✅ Deploy Preview for iotmapcomponent ready!

Name	Link
🔨 Latest commit	`af0e716`
🔍 Latest deploy log	https://app.netlify.com/sites/iotmapcomponent/deploys/6602c1f5afc1590008314b1e
😎 Deploy Preview	https://deploy-preview-184--iotmapcomponent.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

julien-deramond · 2024-03-26T12:37:40Z

@dependabot rebase

Bumps the angular-all-deps group in /test/angular with 11 updates: | Package | From | To | | --- | --- | --- | | [@angular/animations](https://github.com/angular/angular/tree/HEAD/packages/animations) | `17.3.0` | `17.3.1` | | [@angular/common](https://github.com/angular/angular/tree/HEAD/packages/common) | `17.3.0` | `17.3.1` | | [@angular/compiler](https://github.com/angular/angular/tree/HEAD/packages/compiler) | `17.3.0` | `17.3.1` | | [@angular/core](https://github.com/angular/angular/tree/HEAD/packages/core) | `17.3.0` | `17.3.1` | | [@angular/forms](https://github.com/angular/angular/tree/HEAD/packages/forms) | `17.3.0` | `17.3.1` | | [@angular/platform-browser](https://github.com/angular/angular/tree/HEAD/packages/platform-browser) | `17.3.0` | `17.3.1` | | [@angular/platform-browser-dynamic](https://github.com/angular/angular/tree/HEAD/packages/platform-browser-dynamic) | `17.3.0` | `17.3.1` | | [@angular/router](https://github.com/angular/angular/tree/HEAD/packages/router) | `17.3.0` | `17.3.1` | | [@angular-devkit/build-angular](https://github.com/angular/angular-cli) | `17.3.0` | `17.3.2` | | [@angular/cli](https://github.com/angular/angular-cli) | `17.3.0` | `17.3.2` | | [@angular/compiler-cli](https://github.com/angular/angular/tree/HEAD/packages/compiler-cli) | `17.3.0` | `17.3.1` | Updates `@angular/animations` from 17.3.0 to 17.3.1 - [Release notes](https://github.com/angular/angular/releases) - [Changelog](https://github.com/angular/angular/blob/main/CHANGELOG.md) - [Commits](https://github.com/angular/angular/commits/17.3.1/packages/animations) Updates `@angular/common` from 17.3.0 to 17.3.1 - [Release notes](https://github.com/angular/angular/releases) - [Changelog](https://github.com/angular/angular/blob/main/CHANGELOG.md) - [Commits](https://github.com/angular/angular/commits/17.3.1/packages/common) Updates `@angular/compiler` from 17.3.0 to 17.3.1 - [Release notes](https://github.com/angular/angular/releases) - [Changelog](https://github.com/angular/angular/blob/main/CHANGELOG.md) - [Commits](https://github.com/angular/angular/commits/17.3.1/packages/compiler) Updates `@angular/core` from 17.3.0 to 17.3.1 - [Release notes](https://github.com/angular/angular/releases) - [Changelog](https://github.com/angular/angular/blob/main/CHANGELOG.md) - [Commits](https://github.com/angular/angular/commits/17.3.1/packages/core) Updates `@angular/forms` from 17.3.0 to 17.3.1 - [Release notes](https://github.com/angular/angular/releases) - [Changelog](https://github.com/angular/angular/blob/main/CHANGELOG.md) - [Commits](https://github.com/angular/angular/commits/17.3.1/packages/forms) Updates `@angular/platform-browser` from 17.3.0 to 17.3.1 - [Release notes](https://github.com/angular/angular/releases) - [Changelog](https://github.com/angular/angular/blob/main/CHANGELOG.md) - [Commits](https://github.com/angular/angular/commits/17.3.1/packages/platform-browser) Updates `@angular/platform-browser-dynamic` from 17.3.0 to 17.3.1 - [Release notes](https://github.com/angular/angular/releases) - [Changelog](https://github.com/angular/angular/blob/main/CHANGELOG.md) - [Commits](https://github.com/angular/angular/commits/17.3.1/packages/platform-browser-dynamic) Updates `@angular/router` from 17.3.0 to 17.3.1 - [Release notes](https://github.com/angular/angular/releases) - [Changelog](https://github.com/angular/angular/blob/main/CHANGELOG.md) - [Commits](https://github.com/angular/angular/commits/17.3.1/packages/router) Updates `@angular-devkit/build-angular` from 17.3.0 to 17.3.2 - [Release notes](https://github.com/angular/angular-cli/releases) - [Changelog](https://github.com/angular/angular-cli/blob/main/CHANGELOG.md) - [Commits](angular/angular-cli@17.3.0...17.3.2) Updates `@angular/cli` from 17.3.0 to 17.3.2 - [Release notes](https://github.com/angular/angular-cli/releases) - [Changelog](https://github.com/angular/angular-cli/blob/main/CHANGELOG.md) - [Commits](angular/angular-cli@17.3.0...17.3.2) Updates `@angular/compiler-cli` from 17.3.0 to 17.3.1 - [Release notes](https://github.com/angular/angular/releases) - [Changelog](https://github.com/angular/angular/blob/main/CHANGELOG.md) - [Commits](https://github.com/angular/angular/commits/17.3.1/packages/compiler-cli) --- updated-dependencies: - dependency-name: "@angular/animations" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: angular-all-deps - dependency-name: "@angular/common" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: angular-all-deps - dependency-name: "@angular/compiler" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: angular-all-deps - dependency-name: "@angular/core" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: angular-all-deps - dependency-name: "@angular/forms" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: angular-all-deps - dependency-name: "@angular/platform-browser" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: angular-all-deps - dependency-name: "@angular/platform-browser-dynamic" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: angular-all-deps - dependency-name: "@angular/router" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: angular-all-deps - dependency-name: "@angular-devkit/build-angular" dependency-type: direct:development update-type: version-update:semver-patch dependency-group: angular-all-deps - dependency-name: "@angular/cli" dependency-type: direct:development update-type: version-update:semver-patch dependency-group: angular-all-deps - dependency-name: "@angular/compiler-cli" dependency-type: direct:development update-type: version-update:semver-patch dependency-group: angular-all-deps ... Signed-off-by: dependabot[bot] <[email protected]>

dependabot bot added the dependencies Pull requests that update a dependency file label Mar 26, 2024

julien-deramond approved these changes Mar 26, 2024

View reviewed changes

dependabot bot force-pushed the dependabot/npm_and_yarn/test/angular/angular-all-deps-658ba33db7 branch from 22b6681 to af0e716 Compare March 26, 2024 12:39

julien-deramond merged commit 3bdb414 into main Mar 26, 2024
5 checks passed

julien-deramond deleted the dependabot/npm_and_yarn/test/angular/angular-all-deps-658ba33db7 branch March 26, 2024 12:40

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): bump the angular-all-deps group in /test/angular with 11 updates #184

chore(deps): bump the angular-all-deps group in /test/angular with 11 updates #184

dependabot bot commented on behalf of github Mar 26, 2024 •

edited

Loading

netlify bot commented Mar 26, 2024 •

edited

Loading

julien-deramond commented Mar 26, 2024

Commit	Description
	`Internal server error: Invalid URL` when using a non localhost IP
	ensure proper resolution of linked SCSS files
	service-worker references non-existent named index output
	update `webpack-dev-middleware` to `6.1.2`

Commit	Description
	only generate `server` directory when SSR is enabled
	typo in allowedHosts warning for unsupported vite options
	avoid transforming empty component stylesheets
	reduce build times for apps with a large number of components when utilizing esbuild-based builders

Commit	Type	Description
c9d436000	fix	`Internal server error: Invalid URL` when using a non localhost IP
59fba38ec	fix	ensure proper resolution of linked SCSS files
27dd8f208	fix	service-worker references non-existent named index output
c12907d92	fix	update `webpack-dev-middleware` to `6.1.2`

chore(deps): bump the angular-all-deps group in /test/angular with 11 updates #184

chore(deps): bump the angular-all-deps group in /test/angular with 11 updates #184

Conversation

dependabot bot commented on behalf of github Mar 26, 2024 • edited Loading

v17.3.1

17.3.1 (2024-03-20)

compiler

compiler-cli

17.3.1 (2024-03-20)

compiler

compiler-cli

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

v17.3.1

17.3.1 (2024-03-20)

compiler

compiler-cli

17.3.1 (2024-03-20)

compiler

compiler-cli

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

v17.3.1

17.3.1 (2024-03-20)

compiler

compiler-cli

17.3.1 (2024-03-20)

compiler

compiler-cli

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

v17.3.1

17.3.1 (2024-03-20)

compiler

compiler-cli

17.3.1 (2024-03-20)

compiler

compiler-cli

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

v17.3.1

17.3.1 (2024-03-20)

compiler

compiler-cli

17.3.1 (2024-03-20)

compiler

compiler-cli

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

v17.3.1

17.3.1 (2024-03-20)

compiler

compiler-cli

17.3.1 (2024-03-20)

compiler

compiler-cli

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

v17.3.1

17.3.1 (2024-03-20)

compiler

compiler-cli

17.3.1 (2024-03-20)

compiler

compiler-cli

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

v17.3.1

17.3.1 (2024-03-20)

compiler

compiler-cli

17.3.1 (2024-03-20)

compiler

dependabot bot commented on behalf of github Mar 26, 2024 •

edited

Loading

`@schematics/angular`

`@angular-devkit/build-angular`

`@schematics/angular`

`@angular-devkit/build-angular`

`@schematics/angular`

`@angular-devkit/build-angular`

`@angular-devkit/build-angular`

`@angular-devkit/build-angular`

`@angular/cli`

`@schematics/angular`

`@angular-devkit/build-angular`

`@schematics/angular`

`@angular-devkit/build-angular`

`@schematics/angular`

`@angular-devkit/build-angular`

`@angular-devkit/build-angular`

`@angular-devkit/build-angular`

`@angular/cli`

netlify bot commented Mar 26, 2024 •

edited

Loading