@bymax-one/nest-queue 1.0.0 → 1.0.1

package/CHANGELOG.md

@@ -7,6 +7,32 @@ versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ---
 
+## [1.0.1] — 2026-07-30
+
+First release published by CI, and therefore the first carrying an npm provenance
+attestation: `1.0.0` had to be published from a maintainer's machine because npm
+trusted publishing requires the package to already exist.
+
+### Documentation
+
+- Troubleshooting entry for `ERR_PNPM_IGNORED_BUILDS: msgpackr-extract` on
+  install. `msgpackr-extract` is a native optional dependency of BullMQ, and pnpm
+  blocks build scripts by default — pnpm 10 warns and installs anyway, pnpm 11
+  turns the same block into an error, so it appears on a pnpm upgrade with no
+  change on the consumer's side. The entry says whose dependency it is, shows both
+  the interactive and the declarative way to approve it, and notes that skipping
+  the build is fine because `msgpackr` falls back to a pure-JavaScript
+  implementation.
+
+### Internal
+
+- The dogfood smoke test installs its throwaway consumer with `--ignore-scripts`
+  and reports the full `spawnSync` outcome — status, signal, spawn error and both
+  streams — on failure. Not shipped in the package; recorded because it is what
+  made the `v1.0.0` release workflow fail after the publish had already succeeded.
+
+---
+
 ## [1.0.0] — 2026-07-30
 
 First public release. The library is feature-complete for the surface described
@@ -120,4 +146,5 @@ v6 peer range.
 
 ---
 
+[1.0.1]: https://github.com/bymaxone/nest-queue/releases/tag/v1.0.1
 [1.0.0]: https://github.com/bymaxone/nest-queue/releases/tag/v1.0.0

package/README.md

@@ -782,6 +782,39 @@ pnpm typecheck && pnpm test:types && pnpm lint && pnpm test:cov:all && \
 
 ## 🩺 Troubleshooting
 
+### `ERR_PNPM_IGNORED_BUILDS: msgpackr-extract` on install (pnpm 11)
+
+Installing this library with **pnpm 11** can stop with:
+
+```
+ERR_PNPM_IGNORED_BUILDS  Ignored build scripts: msgpackr-extract@3.0.4
+Run "pnpm approve-builds" to pick which dependencies should be allowed to run scripts.
+```
+
+Nothing is wrong with your setup. `msgpackr-extract` is a native optional dependency
+of BullMQ, and pnpm blocks build scripts by default. **pnpm 10 warns and installs
+anyway; pnpm 11 turns the same block into an error**, which is why this appears on
+an upgrade with no change on your side. It is BullMQ's dependency, not this
+package's: this package ships zero runtime dependencies.
+
+Approve it once, either interactively:
+
+```bash
+pnpm approve-builds
+```
+
+or declaratively in your `pnpm-workspace.yaml`:
+
+```yaml
+onlyBuiltDependencies:
+  - msgpackr-extract
+```
+
+Skipping the build is also fine — `msgpackr` falls back to a pure-JavaScript
+implementation, so BullMQ still works, just without the native accelerator.
+
+---
+
 ### `CONNECTION_REQUIRES_NULL_RETRIES`
 
 This error fires in Mode A when the injected client was not configured with

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bymax-one/nest-queue",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "NestJS dynamic module wrapping BullMQ — typed jobs, flows, job schedulers, deduplication, OpenTelemetry, graceful shutdown",
   "author": "Bymax One <support@bymax.one>",
   "license": "MIT",