v1.0.0

First public release. The library is feature-complete for the surface described
in docs/technical_specification.md, holds 100% line/branch/function/statement
coverage, and ships with zero runtime dependencies.

Added

• BymaxQueueModule.forRoot() and .forRootAsync() dynamic module (built on
  ConfigurableModuleBuilder; isGlobal mapped to DynamicModule.global via setExtras)
• QueueService with typed enqueue (native deduplication options), enqueueBulk,
  getJob, getJobs, getMetrics, pauseQueue/resumeQueue/cleanQueue, and Job
  Schedulers upsertJobScheduler/removeJobScheduler/getJobSchedulers
• @Processor, @Process, @OnWorkerEvent (worker-local, full Job), @OnQueueEvent
  (global) decorators plus automatic discovery via DiscoveryService; job.updateProgress()
  and progress event support
• WorkerRegistry programmatic API, including registerSandboxed for file-based
  out-of-process processors
• FlowService (opt-in via options.flows.enabled)
• MetricsService with TTL cache (opt-in via options.metrics.enabled)
• Optional OpenTelemetry telemetry passthrough (via bullmq-otel, an optional peer dep)
• QueueLifecycle bounded graceful-shutdown protocol (bounded drain via Promise.race +
  worker.close(true), optional drain, Redis disconnect on Mode B); at-least-once semantics
  documented
• Dual-mode connection (Mode A: bring-your-own ioredis / Mode B: lib-owned), with per-role
  maxRetriesPerRequest policy applied automatically
• Subpaths: . (server), ./shared (zero-dep types and constants)
• 'error' as a subscribable @OnQueueEvent name. It carries a real Error
  instance rather than the serialized payload every other queue event delivers,
  because it reports a connection fault rather than a job transition
• Peer deps: @nestjs/common ^11, @nestjs/core ^11, bullmq ^5.16, ioredis ^5,
  reflect-metadata ^0.2; optional bullmq-otel ^1
• E2E tests with Testcontainers Redis

Fixed

• The configured prefix now reaches every BullMQ object. Only the producer
  Queue received options.prefix; the Worker, QueueEvents and FlowProducer
  were constructed without it and fell back to BullMQ's default bull prefix. With
  any non-default prefix, producers and consumers diverged onto separate keyspaces —
  workers never consumed jobs, event listeners never fired, and flow jobs were
  enqueued where no worker polled. Nothing threw.

• Explicit @Inject on every injectable constructor parameter. The package
  ships as a tsup/esbuild bundle, and esbuild does not emit
  emitDecoratorMetadata. Providers resolved purely by reflected type metadata
  (QueueService, WorkerRegistry, QueueEventsRegistry,
  ProcessorDiscoveryService, QueueLifecycle) could not be instantiated from
  the built dist by a consumer's Nest container.

• The exports map hands CommonJS consumers CommonJS declarations. With
  "type": "module", TypeScript reads a bare .d.ts as ESM, so a require()
  consumer landed on ESM declarations. types is now declared per condition,
  main/module/types are present for legacy resolution, ./package.json is
  exported, and the package passes attw at the strict profile.

• Every BullMQ emitter the library creates carries a fallback error listener.
  Queue, Worker, QueueEvents and FlowProducer extend Node's EventEmitter,
  where emitting 'error' with no listener throws rather than being delivered.
  The library constructs all four on the consumer's behalf, so a transient Redis
  fault surfaced as an uncaught exception in an application that never asked for
  the emitter. The fallback logs and does not consume the event — an
  @OnWorkerEvent('error') or @OnQueueEvent('error') handler still runs.

• One owner for shutdown. QueueService, FlowService and ConnectionResolver
  each exposed onModuleDestroy, and NestJS binds lifecycle hooks by method name,
  so Nest invoked them on its own schedule while QueueLifecycle also called two
  of them inside its ordered sequence: the flow producer closed twice, and queues
  could close before the bounded drain finished with them. They now expose plain
  methods — QueueService.closeAll(), FlowService.close(),
  ConnectionResolver.teardown() — and QueueLifecycle is the only lifecycle hook.

• Operational failures no longer masquerade as a bad cron. upsertJobScheduler
  wrapped every failure in INVALID_REPEAT_OPTIONS with HTTP 400 and "pattern must
  be a valid cron expression", so an unreachable Redis was reported as a client
  mistake — with a status telling the caller not to retry. Faults carrying a string
  code now propagate untouched.

• A malformed repeat raises the documented error instead of a TypeError.
  The union forbids it for a TypeScript caller, but plain JavaScript and any
  payload cast from unknown reached the in operator unchecked. null,
  undefined, strings, numbers and arrays are rejected as
  INVALID_REPEAT_OPTIONS, as is a blank pattern.

• QueueEventsRegistry.getConnections() returns a copy. ReadonlyMap is a
  compile-time claim only; the live registry could be cast and mutated.

Security

• Release pipeline gated behind a manual-approval environment, with SHA-pinned
  actions, tag/version verification, and OIDC provenance from the second release
  onward.

---

BullMQ version policy

1.x — floor bullmq ^5.16.0

The 1.x series floors peerDependencies.bullmq at ^5.16.0, the release that
introduced the Job Schedulers API (upsertJobScheduler/removeJobScheduler/getJobSchedulers).
Current recommended peer: 5.79.1.

Forward compatibility with BullMQ v6

This library is forward-compatible with BullMQ v6 by design. It exclusively uses
Job Schedulers for recurring jobs and never calls the removed addRepeatable/removeRepeatable
API, so no public-API break is expected on promotion to v6.

Promotion trigger. When the E2E suite is green on both the v5 and v6 matrix, the peer
range will be widened to ^5.16.0 || ^6.0.0 in a minor release. No adapter is needed because
the recurring-jobs surface is unchanged.

Fallback. If another API used by the library breaks in BullMQ v6 without a trivial adapter,
a parallel branch will keep the 1.x line on ^5.16 only, and a 2.x series will track the
v6 peer range.