Skip to content
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

chore(deps): update angular monorepo to v16.0.0-next.5 (patch) #5350

Closed
wants to merge 4 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 30, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@angular/animations 16.0.0-next.4 -> 16.0.0-next.5 age adoption passing confidence
@angular/common 16.0.0-next.4 -> 16.0.0-next.5 age adoption passing confidence
@angular/compiler 16.0.0-next.4 -> 16.0.0-next.5 age adoption passing confidence
@angular/compiler-cli (source) 16.0.0-next.4 -> 16.0.0-next.5 age adoption passing confidence
@angular/core 16.0.0-next.4 -> 16.0.0-next.5 age adoption passing confidence
@angular/forms 16.0.0-next.4 -> 16.0.0-next.5 age adoption passing confidence
@angular/platform-browser 16.0.0-next.4 -> 16.0.0-next.5 age adoption passing confidence
@angular/platform-browser-dynamic 16.0.0-next.4 -> 16.0.0-next.5 age adoption passing confidence
@angular/router (source) 16.0.0-next.4 -> 16.0.0-next.5 age adoption passing confidence

Release Notes

angular/angular

v16.0.0-next.5

Compare Source

Breaking Changes

bazel
  • Several changes to the Angular Package Format (APF)
    • Removal of FESM2015
    • Replacing ES2020 with ES2022
    • Replacing FESM2020 with FESM2022
  • Several changes to the Angular Package Format (APF)
    • Removal of FESM2015
    • Replacing ES2020 with ES2022
    • Replacing FESM2020 with FESM2022
common
  • If the 'ngTemplateOutletContext' is different from the context, it will result in a compile-time error.

Before the change, the following template was compiling:

interface MyContext {
  $implicit: string;
}

@​Component({
  standalone: true,
  imports: [NgTemplateOutlet],
  selector: 'person',
  template: `
    <ng-container
      *ngTemplateOutlet="
        myTemplateRef;
        context: { $implicit: 'test', xxx: 'xxx' }
      "></ng-container>
  `,
})
export class PersonComponent {
  myTemplateRef!: TemplateRef<MyContext>;
}

However, it does not compile now because the 'xxx' property does not exist in 'MyContext', resulting in the error: 'Type '{ $implicit: string; xxx: string; }' is not assignable to type 'MyContext'.'

The solution is either:

  • add the 'xxx' property to 'MyContext' with the correct type or
  • add '$any(...)' inside the template to make the error disappear. However, adding '$any(...)' does not correct the error but only preserves the previous behavior of the code.
core
    • entryComponents has been deleted from the @NgModule and @Component public APIs. Any usages can be removed since they weren't doing anyting.
    • ANALYZE_FOR_ENTRY_COMPONENTS injection token has been deleted. Any references can be removed.
  • ComponentRef.setInput will only set the input on the
    component if it is different from the previous value (based on Object.is
    equality). If code relies on the input always being set, it should be
    updated to copy objects or wrap primitives in order to ensure the input
    value differs from the previous call to setInput.

Deprecations

core
  • makeStateKey, StateKey and TransferState exports have been moved from @angular/platform-browser to @angular/core. Please update the imports.
- import {makeStateKey, StateKey, TransferState} from '@&#8203;angular/platform-browser';
+ import {makeStateKey, StateKey, TransferState} from '@&#8203;angular/core';
  • The @Directive/@Component moduleId property is now
    deprecated. It did not have any effect for multiple major versions and
    will be removed in v17.
platform-server
  • PlatformConfig.baseUrl and PlatformConfig.useAbsoluteUrl platform-server config options are deprecated as these were not used.
common
Commit Type Description
6499f5ae28 fix invalid ImageKit transformation (#​49201)
d47fef72cb fix strict type checking for ngtemplateoutlet (#​48374)
compiler
Commit Type Description
1829542aea fix do not unquote CSS values (#​49460)
73d2f3c866 fix handle trailing comma in object literal (#​49535)
compiler-cli
Commit Type Description
03d1d00ad9 feat Add an extended diagnostic for nSkipHydration (#​49512)
core
Commit Type Description
89d291c367 feat add assertInInjectionContext (#​49529)
605c536420 feat add migration to remove moduleId references (#​49496)
9c5fd50de4 feat effects can optionally return a cleanup function (#​49625)
c024574f46 feat expose makeStateKey, StateKey and TransferState (#​49563)
9b65b84cb9 feat Mark components for check if they read a signal (#​49153)
585e34bf6c feat remove entryComponents (#​49484)
be23b7ce65 fix ComponentRef.setInput only sets input when not equal to previous (#​49607)
316c91b1a4 fix deprecate moduleId @Component property (#​49496)
fdafdb78dc fix set style property value to empty string instead of an invalid value (#​49460)
http
Commit Type Description
45a6ac09fd fix force macro task creation during HTTP request (#​49546)
migrations
Commit Type Description
5e5dac278d feat Migration to remove Router guard and resolver interfaces (#​49337)
platform-browser
Commit Type Description
e8e36811d5 fix set nonce attribute in a platform compatible way (#​49624)
platform-server
Commit Type Description
e99460865e refactor deprecate useAbsoluteUrl and baseUrl (#​49546)
router
Commit Type Description
2dbf3e0023 fix Ensure Router preloading works with lazy component and static children (#​49571)
d3018c0ee7 fix fix #​49457 outlet activating with old info (#​49459)
1600687fe5 fix Route matching should only happen once when navigating (#​49163)

Special Thanks

Alan Agius, Alex Rickabaugh, Andrew Kushnir, Andrew Scott, Asaf Malin, Jan Cabadaj, Jessica Janiuk, JiaLiPassion, Kristiyan Kostadinov, Matthieu Riegler, Paul Gschwendtner, Pawel Kozlowski, Sid, Tano Abeleyra and tomalaforge


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Mar 30, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: e2e/a16/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: jest-preset-angular@13.0.1
npm ERR! Found: @angular-devkit/build-angular@16.0.0-next.6
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   dev @angular-devkit/build-angular@"16.0.0-next.6" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular-devkit/build-angular@">=13.0.0 <16.0.0" from jest-preset-angular@13.0.1
npm ERR! node_modules/jest-preset-angular
npm ERR!   dev jest-preset-angular@"13.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular-devkit/build-angular@15.2.4
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   peer @angular-devkit/build-angular@">=13.0.0 <16.0.0" from jest-preset-angular@13.0.1
npm ERR!   node_modules/jest-preset-angular
npm ERR!     dev jest-preset-angular@"13.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2023-04-01T06_56_53_120Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate-cache/others/npm/_logs/2023-04-01T06_56_53_120Z-debug-0.log

@codecov
Copy link

codecov bot commented Mar 30, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (b2954e0) 100.00% compared to head (49b9a04) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #5350   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          224       224           
  Lines         4773      4773           
  Branches      1090      1090           
=========================================
  Hits          4773      4773           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@renovate renovate bot force-pushed the renovate/e2e/a16/patch-angular-monorepo branch from 4d8d637 to ea108c0 Compare April 1, 2023 06:53
@renovate renovate bot force-pushed the renovate/e2e/a16/patch-angular-monorepo branch from ea108c0 to 3af5b42 Compare April 1, 2023 06:57
@renovate
Copy link
Contributor Author

renovate bot commented Apr 1, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

satanTime added a commit to satanTime/ng-mocks that referenced this pull request Apr 1, 2023
satanTime added a commit to satanTime/ng-mocks that referenced this pull request Apr 15, 2023
satanTime added a commit to satanTime/ng-mocks that referenced this pull request Apr 15, 2023
satanTime added a commit to satanTime/ng-mocks that referenced this pull request Apr 15, 2023
satanTime added a commit to satanTime/ng-mocks that referenced this pull request Apr 15, 2023
satanTime added a commit to satanTime/ng-mocks that referenced this pull request Apr 15, 2023
satanTime added a commit that referenced this pull request Apr 15, 2023
fix(a16): supporting required inputs #5350
@satanTime
Copy link
Member

v14.9.0 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.

@satanTime satanTime deleted the renovate/e2e/a16/patch-angular-monorepo branch April 15, 2023 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant