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 @rxweb/reactive-form-validators to v2.1.8 #803

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 25, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@rxweb/reactive-form-validators (source) 2.1.2 -> 2.1.8 age adoption passing confidence

Release Notes

rxweb/rxweb (@​rxweb/reactive-form-validators)

v2.1.8: 2.1.8(2023-05-04)

Compare Source

Enhancements

  • expose minTime and maxTime validation config value #​630

Special thanks to @​alizedebray for https://github.com/rxweb/rxweb/pull/624.

v2.1.7: 2.1.7(2022-05-09)

Compare Source

Bug Fixes

Enhancement

  • Display error messages with friendly names #​518
  • Auto-Create Prop Object or create with default value #​551
  • updateOn decorator to set validator trigger event #​404

Special thanks to @​pranavirabatti for pull request.

v2.1.6

Compare Source

v2.1.5

Compare Source

v2.1.4: 2.1.4(2021-09-09)

Bug Fixes

  • Show validation with custom parameters #​515
  • Incorrect FormGroup validation state #​510
  • Incorrect marking FormControl state #​508
  • Conditional expression validation state #​505 #​441
  • baseConfig dataFormat missing in minDate Validation #​471
  • add configured minSize value in the fileSize validator #​483
  • Url Validation with subdomain #​493
  • oneOf validation on string value #​432

Enhancement

  • Validate multiple values in StartsWith,EndsWith, and Contains Validator #​457
  • expose date format validation #​447
  • Password validation with special characters #​486

Special thanks to @​branchjoshua for pull request.


Configuration

📅 Schedule: Branch creation - "after 7am and before 11am every weekday" in timezone Europe/London, 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 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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Oct 25, 2023
@renovate
Copy link
Author

renovate bot commented Oct 25, 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: 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: @angular/[email protected]
npm ERR! node_modules/@angular/compiler
npm ERR!   @angular/compiler@"^15.2.9" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler@"^11.0.0" from [email protected]
npm ERR! node_modules/ng-packagr
npm ERR!   dev ng-packagr@"^11.2.4" 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/worker/8ab30d/5acebb/cache/others/npm/_logs/2023-10-25T09_28_40_941Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/8ab30d/5acebb/cache/others/npm/_logs/2023-10-25T09_28_40_941Z-debug-0.log

Copy link
Author

renovate bot commented May 15, 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/ngx-pagination
npm error   ngx-pagination@"^6.0.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer ngx-pagination@"^3.2.1" from @hmcts/[email protected]
npm error node_modules/@hmcts/rpx-xui-common-lib
npm error   @hmcts/rpx-xui-common-lib@"2.0.18-angular-upgrade-17" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-06-26T13_16_40_384Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-26T13_16_40_384Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file ns:xui prd:xui rel:xui-ao-webapp-pr-803
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants