chore(deps): update dependency set-interval-async to v3 #121
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.0.33
->^3.0.3
Release Notes
ealmansi/set-interval-async (set-interval-async)
v3.0.3
Compare Source
What's Changed
v3.0.2
Compare Source
What's Changed
v3.0.1
Compare Source
What's Changed
Breaking Changes
Full Changelog: ealmansi/set-interval-async@v2.0.3...v3.0.1
v3.0.0
Compare Source
v2.0.3
: Relese Notes: v2.0.3Compare Source
Bug fixes:
clearIntervalAsync
with a valid timer.v2.0.2
Compare Source
v2.0.1
Compare Source
v2.0.0
: Relese Notes: v2.0.0Breaking changes
Error handling
Errors thrown by the handler function passed in to
setIntervalAsync
are no longer hidden (swallowed). This will allow users of this library to more easily detect and handle failure within their handlers, which will now raise anUnhandledPromiseRejectionWarning
if not handled by the application itself. If you wish to fall back to the previous behaviour, you may simply wrap your handlers in the following way:Bug fixes
Awaiting
clearIntervalAsync
While
clearIntervalAsync
was still correctly clearing the execution interval, a bug in version v1.x.x was causing the promise returned by the function to be resolved prematurely before the interval was fully stopped. This bug has now been fixed, which means the following code should work as expected: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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.