Update nodemon: 2.0.6 → 2.0.14 (patch) #56
Closed
Conversation
This file contains hidden or 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
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ nodemon (2.0.6 → 2.0.14) · Repo
Release Notes
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 68 commits:
fix: add windows signals SIGUSR2 & SIGUSR1 to terminate the process (#1938)docs: Fix typo in faq.mdchore: update supporterschore: add supporterchore: add releasercchore: set release workflow node versionchore: fix workflow branchfix: release process on mainfix: bump update-notifierchore: supporterschore: new supporterMerge branch 'main' of github.com:remy/nodemonchore: new supporterdocs(installation): Minor Improvementschore: add supporterchore: new supporterchore: clean a logochore: new supporterchore: tweak supporter messagefix(windows): properly handle quoted args in eventMerge branch 'master' of github.com:remy/nodemonfix: ensure numerical OS version checkchore: update issue templatechore: fix stale.ymlchore: move workflow to dirchore: update stalebotfix: windows 8 doesn't support windows-killMerge branch 'master' of github.com:remy/nodemonchore: new supportersfix: allow windows users to install globally again (#1874)chore: updating release process…chore: update semver packageschore: tweak release cichore: readmechore: fix supporter image layoutchore: add semantic release via github actionsMerge branch 'master' of github.com:remy/nodemonchore: add supporterchore: create github action testsMerge branch 'master' of github.com:remy/nodemonchore: new supportersfix: add support for SIGINT on Windows (fixes issue #1720) (#1853)chore: +supporterchore: supporterschore: adding supporterschore: add supporterdocs: adding supporterdocs: add supportersdocs: add supportersdocs: delay option as number instead of string, in readme (#1840)refactor: define the message in one place (#1847)chore: add favicon to web sitedocs: readme dancedocs: web site updatedocs: clean up readmedocs: new sponsorsdocs: update with new sponsorsdocs: update logodocs: add new sponsorMerge branch 'master' of github.com:remy/nodemondocs: update sponsorsdocs: Remove duplicate info about using the `main`fix: redirect help (#1825)chore: update commitlint (#1824)chore: update website codechore: mergechore: update commitlintfix: postinstall hide message in CI👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands