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 ramda to ^0.30.0 #216

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 11, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ramda (source) ^0.27.2 -> ^0.30.0 age adoption passing confidence
@types/ramda (source) 0.27.34 -> 0.30.2 age adoption passing confidence

Release Notes

ramda/ramda (ramda)

v0.30.1: v.0.30.1

Compare Source

upgrade guide: https://github.com/ramda/ramda/issues/3472

v0.30.0

Compare Source

Upgrade guide: https://github.com/ramda/ramda/issues/3453

v0.29.1

Compare Source

Upgrade guide: https://github.com/ramda/ramda/issues/3415

v0.29.0

Compare Source

Added

🆕 addIndexRight
🆕 isNotNil
🆕 swap
🆕 dropRepeatsBy

Removed

Deprecated

Changes

⚠️ propEq/pathEq parameter order

  • Documentation improvements
  • Transducer updates
  • Some support for types
  • Many more!

Thank you to everyone who contributed to this release!

v0.28.0

Compare Source

A long-overdue release with many updates, documented in https://github.com/ramda/ramda/issues/3218.


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 was generated by Mend Renovate. View the repository job log.

Copy link
Author

renovate bot commented Dec 11, 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: frontend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @agm/[email protected]
npm error Found: @angular/[email protected]
npm error node_modules/@angular/common
npm error   @angular/common@"^15.2.10" from the root project
npm error   peer @angular/common@"^15.0.0 || ^16.0.0" from @angular/[email protected]
npm error   node_modules/@angular/cdk
npm error     @angular/cdk@"^15.2.9" from the root project
npm error     peer @angular/cdk@"15.2.9" from @angular/[email protected]
npm error     node_modules/@angular/material
npm error       @angular/material@"^15.2.9" from the root project
npm error       1 more (ngx-ui-tour-md-menu)
npm error     1 more (ngx-ui-tour-md-menu)
npm error   17 more (@angular/forms, @angular/material, ...)
npm error
npm error Could not resolve dependency:
npm error peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/[email protected]
npm error node_modules/@agm/core
npm error   @agm/core@"^3.0.0-beta.0" from the root project
npm error   peer @agm/core@"3.0.0-beta.0" from @agm/[email protected]
npm error   node_modules/@agm/snazzy-info-window
npm error     @agm/snazzy-info-window@"^3.0.0-beta.0" from the root project
npm error
npm error Conflicting peer dependency: @angular/[email protected]
npm error node_modules/@angular/common
npm error   peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/[email protected]
npm error   node_modules/@agm/core
npm error     @agm/core@"^3.0.0-beta.0" from the root project
npm error     peer @agm/core@"3.0.0-beta.0" from @agm/[email protected]
npm error     node_modules/@agm/snazzy-info-window
npm error       @agm/snazzy-info-window@"^3.0.0-beta.0" 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-05-03T21_26_41_533Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-03T21_26_41_533Z-debug-0.log

@renovate renovate bot force-pushed the renovate/ramda-0.x branch from 66be66d to 399972e Compare December 11, 2023 17:05
@renovate renovate bot force-pushed the renovate/ramda-0.x branch from 399972e to 568929a Compare January 22, 2024 04:16
@renovate renovate bot force-pushed the renovate/ramda-0.x branch from 568929a to 5e99b25 Compare March 2, 2024 20:02
@renovate renovate bot force-pushed the renovate/ramda-0.x branch from 5e99b25 to cfd8d2f Compare March 30, 2024 19:31
@renovate renovate bot force-pushed the renovate/ramda-0.x branch from cfd8d2f to 3f536c9 Compare April 28, 2024 01:03
@renovate renovate bot changed the title fix(deps): update dependency ramda to ^0.29.0 fix(deps): update dependency ramda to ^0.30.0 Apr 28, 2024
@renovate renovate bot force-pushed the renovate/ramda-0.x branch from 3f536c9 to 284ac77 Compare May 3, 2024 21:26
@renovate renovate bot force-pushed the renovate/ramda-0.x branch from 284ac77 to f4e6ca3 Compare July 6, 2024 02:45
Copy link
Author

renovate bot commented Jul 6, 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: frontend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @agm/[email protected]
npm error Found: @angular/[email protected]
npm error node_modules/@angular/common
npm error   @angular/common@"^15.2.10" from the root project
npm error   peer @angular/common@"^15.0.0 || ^16.0.0" from @angular/[email protected]
npm error   node_modules/@angular/cdk
npm error     @angular/cdk@"^15.2.9" from the root project
npm error     peer @angular/cdk@"15.2.9" from @angular/[email protected]
npm error     node_modules/@angular/material
npm error       @angular/material@"^15.2.9" from the root project
npm error       1 more (ngx-ui-tour-md-menu)
npm error     1 more (ngx-ui-tour-md-menu)
npm error   17 more (@angular/forms, @angular/material, ...)
npm error
npm error Could not resolve dependency:
npm error peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/[email protected]
npm error node_modules/@agm/core
npm error   @agm/core@"^3.0.0-beta.0" from the root project
npm error   peer @agm/core@"3.0.0-beta.0" from @agm/[email protected]
npm error   node_modules/@agm/snazzy-info-window
npm error     @agm/snazzy-info-window@"^3.0.0-beta.0" from the root project
npm error
npm error Conflicting peer dependency: @angular/[email protected]
npm error node_modules/@angular/common
npm error   peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/[email protected]
npm error   node_modules/@agm/core
npm error     @agm/core@"^3.0.0-beta.0" from the root project
npm error     peer @agm/core@"3.0.0-beta.0" from @agm/[email protected]
npm error     node_modules/@agm/snazzy-info-window
npm error       @agm/snazzy-info-window@"^3.0.0-beta.0" 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-08-26T16_29_57_082Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-08-26T16_29_57_082Z-debug-0.log

@renovate renovate bot force-pushed the renovate/ramda-0.x branch from f4e6ca3 to a4cc10b Compare August 26, 2024 16:30
@renovate renovate bot changed the title fix(deps): update dependency ramda to ^0.30.0 Update dependency ramda to ^0.30.0 Dec 31, 2024
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