feat(queue): migrate to BullMQ 6, ioredis 6 and latest tooling

[msalvatti]

Summary

Clean migration of @bymax-one/nest-queue to the newest majors of its Redis/BullMQ stack, released
as 1.2.0. There is no downstream consumer yet, so the peers move straight to the new majors with
no back-compat ranges. Verified end-to-end and independently audited.

Changes

• Peers → newest majors: bullmq ^6.0.0, bullmq-otel ^2.0.0, ioredis ^6.0.0.
• 'paused' job state removed (BullMQ 6 dropped it — paused-queue jobs now live in 'wait'):
  gone from the JobStatus union, JOB_STATUS, getMetrics().counts, and CleanableStatus. The
  queue-lifecycle events 'paused'/'resumed' (@OnQueueEvent) and pauseQueue/resumeQueue
  are unchanged — those describe the queue, not a job.
• ioredis 6 RESP3 typing fix in connection-resolver.service.ts: a derived options type
  reconstructs the constructor's non-undefined replyMapping requirement (no any, no
  suppression). ioredis 6 keeps 'legacy' reply mapping by default, so getJobCounts/clean/getJobs
  reply shapes are unaffected.
• Dev tooling: eslint ^10, typescript ^6, @types/node ^26, @eslint/js ^10.
• Mutation gate tightened: Stryker break/high 95/99 → 100.
• Docs: README + technical_specification.md updated to BullMQ 6 (branding, peer tables,
  install instructions, §14.5 decision, example manifests). CHANGELOG finalized as [1.2.0].

Breaking changes

Requires bullmq ^6, bullmq-otel ^2, ioredis ^6; the 'paused' job status is removed from
JobStatus, JOB_STATUS, and getMetrics().counts. Shipped as a minor by choice — the changes
would normally warrant a major, but the package has no consumer yet; the CHANGELOG spells out every
breaking detail for a first adopter.

Verification (all green, run locally)

• typecheck, test:types, lint (eslint 10), build (tsup), check:exports, check:mutants,
  check:published — pass.
• test:cov:all — 100% on all four axes (565/565, 231/231, 126/126, 520/520), 281 tests.
• mutation:full (cold) — 100.00%, 0 survived, 0 no-coverage, break: 100.

Notes for the reviewer

• TypeScript 7 is held at 6.0.3 on purpose. ts-jest peer is >=4.3 <7 and the whole
  test/mutation stack runs through it; TS 7 removed the classic compiler API these tools use.
  Support returns with ts-jest's TS 7.1 update (~Oct 2026).
• pnpm-workspace.yaml waives the release-age soak for bullmq@6.0.10 (a fresh major) via
  minimumReleaseAgeExclude, to adopt it now.
• Independently audited (fresh-context agent, against the official BullMQ v6 docs): no blockers;
  it independently re-ran every gate and confirmed 100%/100%. The one must-fix it found — stale
  BullMQ-5 version strings in README/spec — is fixed in this PR.
• Known pre-existing carve-out: Stryker's mutate glob excludes src/server/decorators/**
  (line/branch-covered but not mutation-tested). Not touched by this migration; flagged for a
  possible follow-up.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	bullmq-otel@​2.0.0
	@​types/​node@​26.2.0
	typescript@​6.0.3
	@​eslint/​js@​10.0.1
	ioredis@​5.11.1 ⏵ 6.0.0
	bullmq@​6.0.10
	eslint@​10.8.1

View full report

[Copilot]

Pull request overview

Migrates the library to BullMQ 6, ioredis 6, and updated tooling while releasing version 1.2.0.

Changes:

• Updates Redis/BullMQ peers and developer tooling.
• Removes the obsolete paused job status and updates metrics/types.
• Tightens mutation thresholds and refreshes documentation.

Reviewed changes

Copilot reviewed 20 out of 21 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
tsconfig.build.json	Handles TypeScript 6 deprecation diagnostics.
test/types/public-api.test-d.ts	Updates the public status contract.
stryker.config.json	Raises mutation thresholds to 100%.
src/shared/types/queue-metrics.types.ts	Updates metrics to five statuses.
src/shared/types/job-status.types.ts	Removes paused from JobStatus.
src/shared/constants/job-status.ts	Removes JOB_STATUS.PAUSED.
src/shared/constants/job-status.spec.ts	Updates status constant assertions.
src/server/services/scheduler-metrics.integration.spec.ts	Updates mocked metrics.
src/server/services/queue.service.ts	Adapts status handling for BullMQ 6.
src/server/services/queue.service.spec.ts	Updates queue metrics tests.
src/server/services/metrics.service.spec.ts	Updates metrics fixtures.
src/server/services/connection-resolver.service.ts	Handles ioredis 6 option typing.
src/server/bymax-queue.module.ts	Clarifies generated token behavior.
src/server/bymax-queue.module.spec.ts	Pins the generated option token.
scripts/check-published-surface.mjs	Supports TypeScript 6 checks.
README.md	Documents BullMQ 6 compatibility.
pnpm-workspace.yaml	Pins upgraded Redis/BullMQ packages.
pnpm-lock.yaml	Resolves upgraded dependencies.
package.json	Updates version, peers, and tooling.
docs/technical_specification.md	Revises the BullMQ compatibility contract.
CHANGELOG.md	Records the 1.2.0 migration.

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[msalvatti]

{ "consecutiveFailures": {}, "flakyReruns": {}, "processedCommentIds": [3753837152, 3753837185, 3753837227, 3753837257, 3753837287, 3753837321, 3753837354, 3753837393, 3753892101], "paused": false, "terminated": true, "note": "All 9 Copilot comments resolved (fixes in 64def55 + 40fbe47; 1 semver kept as deliberate 1.2.0). CI green (16 pass, 3 neutral skips) incl. E2E + consumer-app typecheck. Local mutation:full 100%. Re-review settled, no new comments. Ready to merge." }

[Copilot]

Pull request overview

Copilot reviewed 21 out of 22 changed files in this pull request and generated 1 comment.

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

Suppressed comments (1)

src/server/bymax-queue.module.spec.ts:105

• This new assertion codifies a string as a DI token, contrary to the repository's symbol-only token contract (for example, BYMAX_QUEUE_OPTIONS in src/server/bymax-queue.constants.ts:7). Configure ConfigurableModuleBuilder with a Symbol-valued optionsInjectionToken and assert that symbol instead; retaining the generated string preserves the silent token-collision risk the convention is intended to prevent.

    expect(MODULE_OPTIONS_TOKEN).toBe('BYMAX_QUEUE_MODULE_OPTIONS')

[Copilot]

Pull request overview

Copilot reviewed 21 out of 22 changed files in this pull request and generated no new comments.

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

Suppressed comments (3)

src/shared/types/job-status.types.ts:13

• BullMQ 6's JobState also includes prioritized and waiting-children. Omitting them means getJobs cannot query priority jobs (which this service can enqueue) or flow parents waiting on children, despite this type claiming to mirror BullMQ's status set. Add both states and update JOB_STATUS, metrics, documentation, and contract tests together.

export type JobStatus = 'waiting' | 'active' | 'completed' | 'failed' | 'delayed'

src/server/services/queue.service.ts:228

• This snapshot still omits BullMQ 6's prioritized and waiting-children counts. Priority jobs are supported by enqueue, and flow parents can remain in waiting-children, so getMetrics() underreports queue depth for supported workloads. Request both states and expose them in QueueMetrics.

      'active',
      'completed',
      'failed',
      'delayed',
    )

src/server/bymax-queue.module.spec.ts:105

• This assertion enshrines a string-valued DI token, contrary to the repository rule that injection tokens use Symbol() to avoid silent collisions. ConfigurableModuleBuilder accepts optionsInjectionToken, so configure it with BYMAX_QUEUE_OPTIONS and assert symbol identity instead of pinning the generated string (then remove the self-aliasing provider).

  it('derives the option token name from the configured module name', () => {
    // The `moduleName` handed to the configurable-module builder shapes the generated option
    // token's identifier. Pinning the concrete name locks that argument: emptying the module
    // name, or dropping the builder's options object entirely, degrades the token to an opaque
    // `CONFIGURABLE_MODULE_OPTIONS[<hash>]`, which this exact-match assertion rejects.
    expect(MODULE_OPTIONS_TOKEN).toBe('BYMAX_QUEUE_MODULE_OPTIONS')