release-notes
release-notes copied to clipboard
Bump rxjs from 7.5.6 to 7.8.1
Bumps rxjs from 7.5.6 to 7.8.1.
Changelog
Sourced from rxjs's changelog.
7.8.1 (2023-04-26)
Bug Fixes
- asapScheduler: No longer stops after scheduling twice during flush (#7198) (1b52405), closes ReactiveX#7196
- throttle: properly handle default ThrottleConfig values (#7176) (ceb821c)
7.8.0 (2022-12-15)
Features
- buffer:
closingNotifiernow supports anyObservableInput(#7073) (61b877a)- delayWhen:
delayWhen'sdelayDurationSelectornow supports anyObservableInput(#7049) (dfd95db)- sequenceEqual:
compareTonow supports anyObservableInput(#7102) (d501961)- share:
ShareConfigfactory properties now supports anyObservableInput(#7093) (cc3995a)- skipUntil:
notifiernow supports anyObservableInput(#7091) (60d6c40)- window:
windowBoundariesnow supports anyObservableInput(#7088) (8c4347c)7.7.0 (2022-12-15)
Features
- distinct:
flushargument now supports anyObservableInput(#7081) (74c9ebd)- repeatWhen:
notifiersupportsObservableInput(#7103) (8f1b976)- retryWhen:
notifiernow supports anyObservableInput(#7105) (794f806)- sample:
notifiernow supports anyObservableInput(#7104) (b18c2eb)7.6.0 (2022-12-03)
Bug Fixes
- schedulers: no longer cause TypeScript build failures when Node types aren't included (c1a07b7)
- types: Improved subscribe and tap type overloads (#6718) (af1a9f4), closes #6717
Features
- onErrorResumeNextWith: renamed
onErrorResumeNextand exported from the top level. (onErrorResumeNextoperator is stil available, but deprecated) (#6755) (51e3b2c)7.5.7 (2022-09-25)
Bug Fixes
- schedulers: improve performance of animationFrameScheduler and asapScheduler (#7059) (c93aa60), closes #7017, related to #7018 and #6674
Performance Improvements
Commits
72bc921chore(publish): 7.8.17748df4Change workflow permissions to be minimally scoped. (#7217)e88a266docs(fromEvent): update the example to match the actual API (#7246)ceb821cfix(throttle): properly handle default ThrottleConfig values (#7176)6adc66fdocs: update Operators overview (#6819)25bde17docs(deprecations): fix typo in breaking changes (#7237)1ce681bdocs(deprecations): fix some typos in Scheduler Argument (#7119)e72b33adocs: improve search for documentation (#6952)04fc128chore(docs): fix url for Ben's website (#7215)49b3460docs: proofread 6-to-7 change summary (#7002)- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
Hi @dependabot[bot]. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: dependabot[bot] Once this PR has been reviewed and has the lgtm label, please assign puerco for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Deploy Preview for kubernetes-sigs-release-notes ready!
| Name | Link |
|---|---|
| Latest commit | 97ddc51edd18bbe4af0106804f67d2a051692f83 |
| Latest deploy log | https://app.netlify.com/sites/kubernetes-sigs-release-notes/deploys/65d33e8fd54e90000880231c |
| Deploy Preview | https://deploy-preview-570--kubernetes-sigs-release-notes.netlify.app/ |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle rotten - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Reopen this PR with
/reopen - Mark this PR as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closed this PR.
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closedYou can:
- Reopen this PR with
/reopen- Mark this PR as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.