-
Notifications
You must be signed in to change notification settings - Fork 0
Update @reactivex/rxjs to the latest version 🚀 #64
base: master
Are you sure you want to change the base?
Conversation
Version 6.1.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 17 commits.
There are 17 commits in total. See the full diff |
Version 6.2.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 71 commits.
There are 71 commits in total. See the full diff |
Version 6.2.0 just got published. |
Version 6.2.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 52 commits.
There are 52 commits in total. See the full diff |
Version 6.2.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 31 commits.
There are 31 commits in total. See the full diff |
Version 6.3.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 102 commits.
There are 102 commits in total. See the full diff |
Version 6.3.1 just got published. |
Version 6.3.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 5 commits.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 52 commits.
There are 52 commits in total. See the full diff |
|
Update to this version instead 🚀 CommitsThe new version differs by 76 commits.
There are 76 commits in total. See the full diff |
|
|
|
|
|
Version 6.0.0 of @reactivex/rxjs was just published.
The version 6.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of @reactivex/rxjs.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 502 commits ahead by 502, behind by 31.
998027bchore(publish): 6.0.0 - update CHANGELOG.mdfc3d891Merge pull request #3591 from benlesh/publish-6.0.081c93ecMerge pull request #3591 from benlesh/publish-6.0.0f21f9dechore(publish): 6.0.0368e3deMerge pull request #3596 from jayphelps/testing29322b7dfeat(testing): testScheduler.run() supports time progression syntax2d5b3b2feat(testing): Add testScheduler.run() helper91088dafix(fromEvent): don't enumerate valid sources (#3594)c23d5d6docs(MIGRATION): fix URL and heading's markdown typos (#3593)d5658ferefactor(webSocket): rename back to webSocket ala 5.0 (#3590)f4d7d02docs(marbles): fix sync group example (#3584)cb38ddffix(websocket): no longer throws errors in operators applied to it (#3577)d267b38Merge pull request #3565 from darthtrevino/task/3563-devcyclec0e7eabfix: merge from masterc87f0d6fix: Remove watch script mentionsThere are 250 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴