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

Update dependency @testing-library/angular to v17 #2205

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 25, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@testing-library/angular 17.0.0 -> 17.3.2 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

testing-library/angular-testing-library (@​testing-library/angular)

v17.3.2

Compare Source

Bug Fixes
  • make wrapper component standalone: false explicitly (#​498) (5a0665f)

v17.3.1

Compare Source

Bug Fixes

v17.3.0

Compare Source

Features

v17.2.2

Compare Source

Bug Fixes

v17.2.1

Compare Source

Bug Fixes

v17.2.0

Compare Source

Features

v17.1.0

Compare Source

Features

v17.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES
  • @testing-library/dom is now a peer dependency of @testing-library/angular.
    This means that you need to install @testing-library/dom separately.

v16.0.0

Compare Source

Features
BREAKING CHANGES

v15.2.0

Compare Source

Features

v15.1.0

Compare Source

Features

v15.0.0

Compare Source

Features
BREAKING CHANGES
  • Requires Angular v17 to test deferrable views.

v14.5.1

Compare Source

Bug Fixes
  • revert methods to test deferrable views (0582c04)

v14.5.0

Compare Source

Features

v14.4.1

Compare Source

Bug Fixes

v14.4.0

Compare Source

Features

v14.3.0

Compare Source

Features

v14.2.0

Compare Source

Features

v14.1.1

Compare Source

Bug Fixes

v14.1.0

Compare Source

Features

v14.0.0

Compare Source

Features
BREAKING CHANGES
  • Use rerender instead of change.
  • Use rerender instead of changeInput.

For more info see https://github.com/testing-library/dom-testing-library/releases/tag/v9.0.0

v13.4.0

Compare Source

Features
  • support ngOnChanges with correct simpleChange object within rerender (#​366) (83c323f), closes #​365

v13.3.0

Compare Source

Features
  • deprecate change and changeInput in favor of rerender (#​371) (dc4c22f)

v13.2.1

Compare Source

Bug Fixes

v13.2.0

Compare Source

Features
  • add initialRoute parameter to avoid resolver issues with using a default route (#​367) (d3407ca)

v13.1.0

Compare Source

Features

v13.0.2

Compare Source

Bug Fixes

v13.0.1

Compare Source

Bug Fixes

v13.0.0

Compare Source

Features
BREAKING CHANGES
  • The render property ɵcomponentImports is not experimental anymore, and is renamed to componentImports

BEFORE:

render(ParentComponent, {
    ɵcomponentImports: [ChildComponent],
});

AFTER:

render(ParentComponent, {
    componentImports: [ChildComponent],
});
  • This change is made to have the same behavior as the run time behavior.

BEFORE:

The ngOnChanges lifecycle is always invoked when a component is rendered.

AFTER:

The ngOnChanges lifecycle is only invoked if a component is rendered with componentProperties.

  • rerender expects properties to be wrapped in an object containing componentProperties (or componentInputs and componentOutputs to have a more fine-grained control).

BEFORE:

await render(PersonComponent, { 
  componentProperties: { 
    name: 'Sarah' 
  }
});

await rerender({ name: 'Sarah 2' });

AFTER:

await render(PersonComponent, { 
  componentProperties: { 
    name: 'Sarah' 
  }
});

await rerender({ 
  componentProperties: { 
    name: 'Sarah 2' 
  }
});
  • BEFORE:

The minimum version of Angular is v14.0.0

AFTER:

The minimum version of Angular is v15.0.0

  • The config property detectChanges is renamed to detectChangesOnRender.

BEFORE:

const component = await render(AppComponent, {
  detectChanges: false
});

AFTER:

const component = await render(AppComponent, {
  detectChangesOnRender: false
});

v12.3.0

Compare Source

Features
  • deprecate detectChanges in favor of detectChangesOnRender (#​340) (63c27e2)

v12.2.2

Compare Source

Bug Fixes
  • disable updateBuildableProjectDepsInPackageJson (65cccbe)

v12.2.1

Compare Source

Bug Fixes

v12.2.0

Compare Source

Features
  • childComponentOverrides property to override nested child providers (#​332) (6e951ad)

v12.1.2

Compare Source

Bug Fixes

v12.1.1

Compare Source

Bug Fixes

v12.1.0

Compare Source

Features
  • support componentImports option for standalone components (experimental) (#​307) (459b500)

v12.0.2

Compare Source

Bug Fixes

v12.0.1

Compare Source

Bug Fixes

v12.0.0

Compare Source

Features
BREAKING CHANGES
  • This version requires Angular v14+

Configuration

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

🚦 Automerge: Disabled because a matching PR was automerged previously.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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


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

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Author

renovate bot commented Jul 25, 2024

⚠️ 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: flink-runtime-web/web-dashboard/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"0.15.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.11.4" from @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"13.4.0" from the root project
npm ERR!   peer @angular/core@"13.4.0" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"13.4.0" 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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-19T10_51_21_989Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 20 times, most recently from 6896f6e to 68f4922 Compare August 1, 2024 09:41
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 9 times, most recently from af4293e to f5a26d9 Compare August 2, 2024 13:29
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 17 times, most recently from 424ea0e to a252ef0 Compare November 13, 2024 11:21
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 11 times, most recently from 5bdaad6 to 9fc537a Compare November 19, 2024 07:18
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from 9fc537a to 3695783 Compare November 19, 2024 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants