chore(deps)(deps): bump @nestjs/schedule from 6.1.3 to 12.0.1 - #190
Closed
dependabot[bot] wants to merge 1 commit into
Closed
chore(deps)(deps): bump @nestjs/schedule from 6.1.3 to 12.0.1#190dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/nestjs/schedule-12.0.1
branch
from
August 31, 2026 07:30
ed02cf9 to
2745286
Compare
Bumps [@nestjs/schedule](https://github.com/nestjs/schedule) from 6.1.3 to 12.0.1. - [Release notes](https://github.com/nestjs/schedule/releases) - [Commits](nestjs/schedule@6.1.3...12.0.1) --- updated-dependencies: - dependency-name: "@nestjs/schedule" dependency-version: 12.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/nestjs/schedule-12.0.1
branch
from
September 1, 2026 10:51
2745286 to
1afcb01
Compare
ihabkhaled
added a commit
that referenced
this pull request
Sep 1, 2026
Coordinated bump of @nestjs/common, core, platform-express, testing, schedule, mongoose and schematics to their v12 releases across all 18 NestJS services and the 4 shared packages that depend on them (closing dependabot PRs #188, #190, #193, #196, which each only bumped one package and left the tree in a broken mixed-version state). NestJS 12's common/core/testing packages ship as pure ESM with no CommonJS build, which this repo's TypeScript config (Node16 module resolution) rejects outright. Verified empirically that the minimal, non-invasive fix is `module: esnext` + `moduleResolution: bundler` in each workspace's tsconfig — TypeScript stops requiring extensions on relative imports (avoiding a rewrite of every import in the codebase), while `"type": "module"` in package.json makes Node's own ESM loader handle the compiled output correctly. tsc-alias's -f flag adds the `.js` extensions to compiled output that Node's loader still needs. Knock-on fixes, each proven with an actual boot (not just a green typecheck): - Prisma's generated client is copied into dist/, not compiled by tsc; a new tools/typescript/copy-generated-prisma.mjs step runs between the compile and the tsc-alias pass so the copy exists before tsc-alias resolves the extension on that import. - Auth-service and routing-service's plain-node Prisma seed scripts (seed.js and friends, using require()) are renamed .cjs, since a parent "type": "module" makes Node parse a bare .js as ESM. prisma.config.ts and the seed/seed:permissions package.json scripts updated to match. - Jest keeps running as CommonJS (switching it to ESM breaks the `jest.mock`/`jest.fn` globals in every spec file) but needs @nestjs/*'s compiled JS transformed back to CJS for tests only, via a babel-jest pass scoped to node_modules/@nestjs plus a reflect-metadata setupFile (v12 no longer pulls it in as a side effect). @babel/core is pinned to the stable v7 line, not v8 -- babel-plugin-transform-import-meta's v8-only release conflicts with this repo's other Babel 7 consumers. - nestjs-pino bumped 4.6.1 -> 5.0.0 (only version whose peer range allows @nestjs/common v12). - @nestjs/throttler has not yet published a v12-compatible peer range (latest is 6.5.0, capped at ^11); Docker's from-scratch dependency install (no lockfile, unlike CI's `npm ci`) needs --legacy-peer-deps to accept that known-safe mismatch, added to every service's Dockerfile and Dockerfile.dev. Verified end-to-end, not just gated: typecheck, lint, build and test green across all 18 services and 6 shared packages, and a real `docker build` + `docker run` of claw-health-service reaches "Nest application successfully started" inside the actual production image. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
Author
|
Looks like @nestjs/schedule is up-to-date now, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/nestjs/schedule-12.0.1
branch
September 1, 2026 13:04
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.
Bumps @nestjs/schedule from 6.1.3 to 12.0.1.
Release notes
Sourced from @nestjs/schedule's releases.
Commits
1df146cchore(): release v12.0.17c241a5Merge pull request #2349 from nestjs/feat/export-schedule-explorer00d3db8feat: export ScheduleExplorer from the package entry point55e94ddMerge pull request #2347 from nestjs/renovate/cimg-node-24.x7e5d551Merge pull request #2348 from nestjs/renovate/nest-monorepo5237ab0chore(deps): update nest monorepo to v12.0.16bd6e14chore(): release v12.0.06719285feat: support nestjs v123bcca07chore(deps): update node.js to v24.20.01b24bb7chore(deps): update nest monorepo to v11.2.3 (#2346)