Open dependabot[bot] opened 3 months ago
node-cron 3.0.1 and 3.0.2 had a memory leak, hence why we are still on 3.0.0 to this day.
I'm still split whether to upgrade or not: 3.0.0 works fine for us, and the 3.0.1 memory leak was a pain to investigate as it was a really slow leak with a cryptic error message. I doubt the improvements in 3.0.3 are really worth the risk.
Bumps node-cron from 3.0.0 to 3.0.3.
Commits
e65a2d0
v3.0.349fed60
Merge pull request #366 from gokulchandra/fixes-memory-leakf6e2436
Merge branch 'master' into fixes-memory-leaka0be3f4
new bugfix versionf370a0d
Merge pull request #356 from Juneezee/fix/uuid-dependency665abde
creates single instance of date formatter5d715f1
fix: add uuid dependency57481d3
bumping dependenciesc7d877d
Merge pull request #341 from node-cron/dependabot/npm_and_yarn/moment-2.29.207938f9
Merge branch 'master' into dependabot/npm_and_yarn/moment-2.29.2Dependabot 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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show