fix(deps): update dependency @nestjs/schedule to v12 - #814
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/nestjs-schedule-12.x
branch
from
September 15, 2026 18:40
e250aa2 to
8ab562a
Compare
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.
This PR contains the following updates:
^6.0.0→^12.0.0Release Notes
nestjs/schedule (@nestjs/schedule)
v12.0.1Compare Source
What's Changed
Full Changelog: nestjs/schedule@12.0.0...12.0.1
v12.0.0Compare Source
What's Changed
@nestjs/scheduleis now a native ES module, and the major version is aligned with the Nest 12 release line (there is no 7.x — 6.1.3 goes straight to 12.0.0).ESM migration
The package is published as pure ESM (
"type": "module", compiled withNodeNext) behind a properexportsmap. The legacy rootindex.js/index.d.ts/index.tsshims are gone, and deep imports into build internals are no longer resolvable — import from the package root.Only
.and./package.jsonare exported.require(esm) — CommonJS still works
You do not need to convert your app to ESM. Thanks to Node's
require(esm)support, a CommonJS app can keep doing:This is why the package now declares
"engines": { "node": ">=20.19.0" }—require(esm)is unflagged from Node 20.19 / 22.12 onward. On older Node versions the require will throwERR_REQUIRE_ESM.Fixes
@Cron,@Interval, or@Timeoutdeclarations sharing an explicit name previously slipped past decorator collection and only conflicted later; theDUPLICATE_SCHEDULERerror is now thrown during initialization, where you can actually see it.Upgrading
index.jsshim path explicitly, drop the path —@nestjs/scheduleresolves on its own.Configuration
📅 Schedule: (UTC)
🚦 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 was generated by Mend Renovate. View the repository job log.