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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency rxjs to v7 - autoclosed #122

Closed
wants to merge 1 commit into from
Closed

chore(deps): update dependency rxjs to v7 - autoclosed #122

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 29, 2021 •
edited

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
rxjs (source) ^6.0.0 -> ^6.0.0 || ^7.0.0 age adoption passing confidence
rxjs (source) 6.6.7 -> 7.2.0 age adoption passing confidence

Release Notes

reactivex/rxjs

v7.2.0

Compare Source

Bug Fixes
  • debounceTime: unschedule dangling task on unsubscribe before complete (#​6464) (7ab0a4c)
  • fromEvent: Types now properly infer when resultSelector is provided (#​6447) (39b9d81)
Features
  • Operators are all exported at the top level, from "rxjs". From here on out, we encourage top-level imports with RxJS. Importing from rxjs/operators will be deprecated soon. (#​6488) (512adc2), closes #​6242

v7.1.0

Compare Source

Bug Fixes
  • returned operator functions from multicast operators share, publish, publishReplay are now referentially transparent. Meaning if you take the result of calling publishReplay(3) and pass it to more than one observable's pipe method, it will behave the same in each case, rather than having a cumulative effect, which was a regression introduced sometime in version 6. If you required this broken behavior, there is a workaround posted here (#​6410) (e2f2e51), closes /github.com/ReactiveX/rxjs/pull/6410#issuecomment-846087374 #​5411
Features
  • All subjects now have an observed property. This will allow users to check whether a subject has current subscribers without us allowing access to the observers array, which is going to be made private in future versions. (#​6405) (f47425d)
  • groupBy: Support named arguments, support ObservableInputs for duration selector (#​5679) (7a99397)
  • share: use another observable to control resets (#​6169) (12c3716)

7.0.1 (2021-05-12)

Bug Fixes
  • bindCallback: resulting function now recreated underlying Subject and is reusable once again. (#​6369) (abf2bc1)
  • retry: properly handles retry counts smaller than 1. (#​6359) (e797bd7)
  • share: properly closes synchronous "firehose" sources. (#​6370) (2271a91)
  • Observable teardowns now properly called if useDeprecatedSynchronousErrorHandling is true. (#​6365) (e19e104), closes #​6364
  • Subscription: properly release parent subscriptions when unsubscribed. (#​6352) (88331d2), closes #​6351 #​6351
  • node: do not reference DOM-related imports to assist in node usage. (#​6305) (b24818e), closes #​6297

v7.0.1

Compare Source

Bug Fixes
  • bindCallback: resulting function now recreated underlying Subject and is reusable once again. (#​6369) (abf2bc1)
  • retry: properly handles retry counts smaller than 1. (#​6359) (e797bd7)
  • share: properly closes synchronous "firehose" sources. (#​6370) (2271a91)
  • Observable teardowns now properly called if useDeprecatedSynchronousErrorHandling is true. (#​6365) (e19e104), closes #​6364
  • Subscription: properly release parent subscriptions when unsubscribed. (#​6352) (88331d2), closes #​6351 #​6351
  • node: do not reference DOM-related imports to assist in node usage. (#​6305) (b24818e), closes #​6297

v7.0.0

Compare Source

Bug Fixes

Configuration

📅 Schedule: 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 WhiteSource Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Apr 29, 2021 •
edited

⚠️ 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 check 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! Found: rxjs@7.0.0
npm ERR! node_modules/rxjs
npm ERR!   dev rxjs@"7.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer rxjs@"^6.0.0" from @nestjs/common@7.6.15
npm ERR! node_modules/@nestjs/common
npm ERR!   dev @nestjs/common@"7.6.15" from the root project
npm ERR!   peer @nestjs/common@"^7.0.0" from @nestjs/core@7.6.15
npm ERR!   node_modules/@nestjs/core
npm ERR!     dev @nestjs/core@"7.6.15" from the root project
npm ERR!     2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR!   2 more (@nestjs/platform-express, @nestjs/testing)
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/2021-05-05T18_06_45_047Z-debug.log

@renovate renovate bot force-pushed the renovate/rxjs-7.x branch 2 times, most recently from 3af7b73 to 7799a80 Compare May 7, 2021 13:49
@renovate
Copy link
Contributor Author

renovate bot commented May 7, 2021 •
edited

⚠️ 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 check 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! Found: rxjs@7.1.0
npm ERR! node_modules/rxjs
npm ERR!   dev rxjs@"7.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer rxjs@"^6.0.0" from @nestjs/common@7.6.17
npm ERR! node_modules/@nestjs/common
npm ERR!   dev @nestjs/common@"7.6.17" from the root project
npm ERR!   peer @nestjs/common@"^7.0.0" from @nestjs/core@7.6.17
npm ERR!   node_modules/@nestjs/core
npm ERR!     dev @nestjs/core@"7.6.17" from the root project
npm ERR!     2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR!   2 more (@nestjs/platform-express, @nestjs/testing)
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/2021-05-21T18_45_31_521Z-debug.log

@renovate renovate bot force-pushed the renovate/rxjs-7.x branch 2 times, most recently from a415f29 to abb56c6 Compare May 14, 2021 11:17
@renovate
Copy link
Contributor Author

renovate bot commented Jul 4, 2021 •
edited

⚠ 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 check 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! Found: rxjs@7.2.0
npm ERR! node_modules/rxjs
npm ERR!   dev rxjs@"7.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer rxjs@"^6.0.0" from @nestjs/common@7.6.18
npm ERR! node_modules/@nestjs/common
npm ERR!   dev @nestjs/common@"7.6.18" from the root project
npm ERR!   peer @nestjs/common@"^7.0.0" from @nestjs/core@7.6.18
npm ERR!   node_modules/@nestjs/core
npm ERR!     dev @nestjs/core@"7.6.18" from the root project
npm ERR!     2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR!   2 more (@nestjs/platform-express, @nestjs/testing)
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/2021-07-05T18_37_02_159Z-debug.log

@renovate renovate bot changed the title chore(deps): update dependency rxjs to v7 chore(deps): update dependency rxjs to v7 - autoclosed Jul 7, 2021
@renovate renovate bot closed this Jul 7, 2021
@renovate renovate bot deleted the renovate/rxjs-7.x branch July 7, 2021 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@renovate-bot