Bump node-schedule from 1.3.2 to 2.0.0 #7
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
the
dependencies
Bumps [node-schedule](https://github.com/node-schedule/node-schedule) from 1.3.2 to 2.0.0. - [Release notes](https://github.com/node-schedule/node-schedule/releases) - [Changelog](https://github.com/node-schedule/node-schedule/blob/master/CHANGELOG.md) - [Commits](node-schedule/node-schedule@v1.3.2...2.0.0) --- updated-dependencies: - dependency-name: node-schedule dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/node-schedule-2.0.0
branch
from
a398f29 to
bd6b07d
Compare
|
Superseded by #60. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/node-schedule-2.0.0
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps node-schedule from 1.3.2 to 2.0.0.
Release notes
Sourced from node-schedule's releases.
Changelog
Sourced from node-schedule's changelog.
Commits
da9aae9Add missing metadata3ea94f0Add changelog22fa7fcEnsure that anonymous job id collision is pretty much impossible (#582)abaae09Avoid leaking memory on one-off jobs (#581)45aeb25Remove id generation since we rely on names being unique (#580)a536cf6Make structure more modular (#579)e1dcfb0Execute airtap tests on a headless Chromium (#578)a1c603eBrowser compatibility (#553)73afccdRemove support for job objects (#557)6697942Provide alternatives for use-cases node-schedules is not intended to be used forMaintainer changes
This version was pushed to npm by kibertoad, a new releaser for node-schedule since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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)