Skip to content

nestarc Changelog: NestJS Package Releases ​

Version history for all nestarc packages. Each package follows Semantic Versioning.

Release Overview ​

These are releases of nestarc's NestJS libraries. For the NestJS framework itself, use the NestJS release history.

The catalog versions of all 15 published packages (14 SaaS libraries and one Labs tool) matched npm's latest tags on 2026-11-15. Publication dates below use UTC. Documented version identifies this site's API scope. Review each package's migration guidance before upgrading, especially idempotency 1.0's coordinated storage cutover.

Package and historynpm latest · publishedDocumented versionCovered changes and next step
tenancy0.16.4 · 2026-11-140.16.4Bind the active tenant inside an audit-owned transaction. Audit and soft-delete setup
safe-response0.16.0 · 2026-10-020.16.0Corrected payload, OpenAPI, status, and deprecation contracts; setup
pagination0.3.2 · 2026-10-270.3.2Corrected keyset traversal, filtered totals, and count-free offset navigation; upgrade
soft-delete0.7.6 · 2026-11-150.7.6Audit-log 0.8.0 / tenancy 0.16.4 compatibility with PostgreSQL isolation and rollback checks; upgrade
idempotency1.0.0 · 2026-10-071.0.0Hashed identities, opaque replay storage, and adapter subpaths; migration
audit-log0.9.0 · 2026-11-150.9.0Atomic PostgreSQL audit-to-Outbox delivery with rollback and consumer deduplication; delivery guide, upgrade
api-keys0.4.0 · 2026-08-310.4.0Prisma 6/7 support; upgrade
feature-flag0.6.0 · 2026-09-100.6.0Repository/tenant providers and corrected rollout targeting; upgrade
rbac0.2.2 · 2026-09-020.2.2Permission and storage fixes; setup
outbox0.4.1 · 2026-10-310.4.1Public poller drain and explicit incomplete-shutdown errors; upgrade
inbox0.2.0 · 2026-10-280.2.0Bounded application-testing helpers and operational recovery checks; schema v2 unchanged; testing
jobs0.4.2 · 2026-10-310.4.2Outbox 0.4 support and verified stop-before-close composition; setup
webhook0.13.3 · 2026-10-290.13.3Correct signing-key provisioning with encrypting vaults; endpoint setup
data-subject0.3.0 · 2026-10-110.3.0Allowlisted export, verified erasure, signed previews, and durable recovery; upgrade, execution paths

The Labs tool @nestarc/mcp-guard 0.2.0, published 2026-05-10 UTC, also matches npm latest. Its tool guide covers configuration scanning and discovery; it uses Apache-2.0 rather than the SaaS packages' MIT license.

The entries below preserve selected release history. The package catalog describes adoption order and support scope; mcp-guard history is listed separately as tooling.

@nestarc/tenancy ​

0.16.4 — 2026-11-14 ​

  • Pass tenancyTransactionCallback(tenancyService, work) to withAuditTransaction() to set the authorized PostgreSQL tenant on the same connection as the business write and its audit record. The wrapper rejects a missing tenant, a root client, and a transaction already bound to another tenant.
  • The PostgreSQL integration test combines tenancy 0.16.4, audit-log 0.7.0, and soft-delete 0.7.5. It covers concurrent tenant isolation, delete and restore operations, and rollback after an audit insert fails.

API reference · Integration guide · Release source

0.16.3 — 2026-11-02 ​

  • Missing-context hooks, diagnostic reporters, and tenancy event listeners handle rejected promises they return. The package logs the failure and preserves synchronous policy enforcement and event dispatch.

Release source

0.16.2 — 2026-10-25 ​

  • Raise the Node.js requirement to ^22.23.4 || ^24.22.1. Upgrade the actual runtime in application processes, containers, CI, and workers; installing tenancy does not patch Node's embedded Brotli decoder. Node 26 support is not declared.
  • Update the application's own body-parser dependency graph to at least 1.20.9 in the 1.x line or 2.4.0 in the 2.x line. The package repository's overrides do not propagate to consumers.
  • Reject empty or ASCII-digit-only TenantResourceKey separators at construction. Default : and other valid separators preserve their exact key format. Stop old readers/writers and migrate affected resources using independently verified tenant ownership before upgrading.
  • Keep NestJS 10/11 and Prisma 6/7 peer ranges unchanged. Upgrading from 0.16.1 requires no database schema or RLS policy migration.

Release source · Security upgrade guide · Resource-key migration

0.16.1 — 2026-09-10 ​

  • Fix PathTenantExtractor for middleware requests that provide a raw url without path; preserve explicit path precedence and strip query strings and fragments.
  • Correct authentication ordering, PostgreSQL RLS bypass boundaries, injection behavior, cache TTL units, and HTTP adapter guidance.
  • Add a complete authenticated Nest/Prisma example, a consumer agent guide, and packaged reference documents with documentation CI.
  • Replace unsupported benchmark headline claims with an explicit disposable-database workflow and a dated raw measurement artifact.

Release source · Patch upgrade guide

0.16.0 — 2026-08-30 ​

  • Breaking: Node.js now requires ^22.13.0 || ^24.0.0; lifecycle event payloads remove raw request in favor of requestSummary.
  • Generate schema-derived TEXT/UUID RLS predicates and a restrictive non-empty-context policy. Existing installations must review and reapply generated SQL; unusual or long identifiers now use collision-resistant names.
  • Reject invalid tenant-column mappings during scaffolding; share the module's validated dbSettingKey across runtime extensions and transactions.
  • Add sync/async TenantIdValidator support to RPC restoration and redacted invalid-context diagnostics.
  • Fix cache-manager 2.x synchronous keys, UUID reset casts, empty TEXT tenant access, and atomic/sequential SQL application.
  • Verify Prisma 6.19.3/7.10.0 and the published NestJS 11/Prisma 7 ecosystem lane. Transparent interactive transactions remain deprecated through 0.16.x and are scheduled for removal in 0.17.

Release source · Migration guide

0.15.0 ​

  • Added tenancy doctor to audit the live application role, RLS state and policies, tenant indexes, grants, and optional read-only tenant-isolation probes
  • Added a real PostgreSQL and PgBouncer transaction-mode matrix for Prisma 6 and 7, covering commit, rollback, timeout, pool contention, backend reuse, and replacement
  • Added one non-HTTP missing-context policy (ignore, warn, or throw) for propagators, interceptors, response caching, Redis/search resource keys, and search adapters
  • Added TenantResourceKey and TenantSearch for collision-safe tenant resource IDs and fail-closed vendor-neutral search access
  • Added maxWait forwarding to tenancyTransaction(); deprecated interactiveTransactionSupport in favor of the public-API helper
  • Added a tarball-installed ecosystem compatibility release gate covering API Keys, RBAC, RLS, Outbox, Jobs, and Webhook flows

0.14.0 ​

  • Added first-class Prisma 7 support with Prisma Config, the prisma-client generator, explicit generated output, and PostgreSQL driver-adapter E2E coverage
  • Added a Prisma 6 compatibility CI lane; Prisma 5 is no longer supported by tenancy
  • Breaking: raised the minimum Node.js version to 20.19
  • Fixed shared extension imports by using @prisma/client/extension

0.13.0 ​

  • Added TenantCacheInterceptor for Nest response cache keys scoped by the current tenant
  • Added @SharedTenantCache() for routes that intentionally share cache entries across tenants
  • Added @nestarc/tenancy/cache subpath exports and optional @nestjs/cache-manager / cache-manager peer metadata
  • Kept the root @nestarc/tenancy entrypoint free of eager cache runtime imports
  • Fixed NestJS 10 middleware wildcard registration while preserving NestJS 11 named wildcard support

0.12.0 ​

  • Breaking: removed deprecated flat cross-check options; use crossCheck: { extractor, onFailed, required }
  • Added engines.node metadata for documented Node.js support
  • Moved prompts to regular dependencies so the interactive CLI works in normal installs
  • Made CLI shebang injection idempotent
  • Added public API smoke coverage for root and testing entrypoints
  • Added v0.12.0 cross-check migration guidance and clarified JWT extraction, @BypassTenancy(), withoutTenant(), and interactive transaction usage

0.8.0 ​

  • Microservice propagation: HTTP, Bull, Kafka, gRPC propagators
  • TenantContextInterceptor for inbound context restoration
  • crossCheckExtractor for tenant ID forgery prevention
  • OpenTelemetry integration (opt-in)
  • Error hierarchy: TenantContextMissingError base class
  • CLI check command for drift detection
  • Multi-schema support (@@schema() directives)

0.7.0 ​

  • failClosed mode for Prisma extension
  • interactiveTransactionSupport option
  • tenancyTransaction() helper for interactive transactions
  • Event system via @nestjs/event-emitter

0.6.0 ​

  • autoInjectTenantId for create/upsert operations
  • sharedModels to skip tenancy extension checks and setup for specific models (database RLS remains active)
  • withoutTenant() programmatic bypass
  • ccTLD-aware subdomain extraction

0.5.0 ​

  • Initial public release
  • 5 built-in extractors (Header, Subdomain, JWT Claim, Path, Composite)
  • AsyncLocalStorage-based tenant context
  • Prisma Client Extension with set_config()
  • CLI init command for RLS scaffolding

@nestarc/safe-response ​

0.16.0 — 2026-10-02 ​

  • Preserve payload immutability for overlapping field selections and correct Swagger contracts for arrays, primitive/null/undefined payloads, validation details, and fallback errors.
  • Preserve Express HTTP errors, including HTTP 413 with PAYLOAD_TOO_LARGE, and use the handler's final success status in envelopes and status mapping.
  • Preserve repeated cursor filters and correct client response guards and /client type resolution.
  • Use RFC 9745 @<unix-timestamp> deprecation dates instead of a nonstandard true fallback. SafeSuccessResponse<T> becomes a conditional type alias; generic extensions should use intersections.
  • Add installed-tarball and HTTP/OpenAPI contract checks across the declared NestJS 10/11, Swagger 8/11, and Node compatibility lanes; replace unsupported performance claims with reproducible benchmark instructions.

Release source · Installation

0.15.0 ​

  • Added createSafeException() for typed SafeException subclasses from defineErrors() catalogs
  • Added ApiSafeCatalogError() and ApiSafeCatalogErrors() Swagger decorators for catalog-backed error documentation
  • Added fieldSelection support to composite decorators and errorFormat: 'safe' | 'problem' for explicit error schema selection
  • Added maxFields and maxFieldLength field selection quotas
  • Hardened field selection against inherited properties and reserved path segments such as __proto__, prototype, and constructor
  • Tightened pagination and rate-limit metadata validation, and avoided double-writing already-sent Express/Fastify error responses

0.14.0 ​

  • Field selection / partial response support via Google-style ?fields=id,name,address.city
  • @FieldSelection() decorator and global fieldSelection module option
  • Error catalog support with defineErrors() and SafeException
  • API version metadata via the version module option
  • Automatic StreamableFile detection to skip response wrapping for file downloads
  • New client guard: hasFieldSelection()

0.13.1 ​

  • Rate limit metadata mirroring (X-RateLimit-* headers)
  • nestjs-cls integration for context injection

0.13.0 ​

  • API deprecation (@Deprecated() decorator) with RFC 9745/8594 headers
  • Composite decorators: @SafeEndpoint(), @SafePaginatedEndpoint(), @SafeCursorPaginatedEndpoint()

0.12.0 ​

  • RFC 9457 Problem Details support
  • Frontend client types (@nestarc/safe-response/client)
  • nestjs-i18n integration

0.11.0 ​

  • Request ID tracking
  • Response time in meta
  • Cursor pagination support (@CursorPaginated())

0.10.0 ​

  • Initial public release
  • Automatic response wrapping
  • Error standardization
  • Offset pagination metadata
  • Swagger integration

@nestarc/audit-log ​

Current documentation status (2026-11-15): 0.9.0. PostgreSQL automatic tracking is Supported for atomic-required writes through withAuditTransaction(); best-effort remains non-atomic. PostgreSQL and SQL Server support manual logging, managed manual transactions, and history queries. SQL Server automatic tracking, scan/export, retention, and partitioning remain unsupported. For atomic soft-delete operations, the PostgreSQL integration guide pins tenancy 0.16.4, audit-log 0.8.0, and soft-delete 0.7.6. Upgrade soft-delete to 0.7.6 before adding audit-log 0.8.0; the earlier peer ranges exclude it. Soft-delete 0.7.6 does not include audit-log 0.9.0 in its peer range, so that lifecycle recipe stays on 0.8.0.

0.9.0 — 2026-11-15 ​

  • Add optional shared delivery configuration and createOutboxAuditDelivery(emitter) for PostgreSQL. Business changes, audit INSERTs and Outbox events use the same managed transaction; enqueue failure prevents commit even when caught.
  • Support the bound manual writer from withManualTransaction() and automatic atomic-required writes through withAuditTransaction(). Existing APIs, SQL Server behavior and standalone installations remain compatible when delivery is omitted; Outbox is not a required runtime dependency.
  • Emit the versioned nestarc.audit.recorded.v1 summary with a stable audit ID and explicit tenant/global scope. Full changes, arbitrary metadata and actor IP are excluded. Receivers deduplicate by tenant and audit ID for at-least-once delivery.
  • Verify rollback, tenant isolation under PostgreSQL RLS, and real Outbox 0.4.1 recovery after producer termination and lost acknowledgements. The registry consumer delivered four attempts with two durable consumer effects and loaded audit-log without Outbox installed.
  • Publish the 0.9.0 API reference and downloadable standalone example. The Outbox path needs its schema installed before enabling delivery; SQL Server delivery, historical backfill, exactly-once execution and commit-order guarantees are outside this release.

Release source · Completed release checks · Atomic Outbox delivery · Upgrade guide

0.8.0 — 2026-10-26 ​

  • Add AuditService.withManualTransaction(client, async ({ tx, log }) => …, options?) for typed business writes and bound manual events. Caught audit failures prevent commit, started log calls settle before completion, and expired writers reject.
  • Add opt-in strictManualValidation, a redacted JSON UTF-8 budget through maxMetadataBytes, and structured AuditInputError diagnostics before INSERT. Existing validation defaults remain unchanged.
  • Add onAuditOperation for content-free operation timing and outcomes, and getCapabilities() for configured provider support without database I/O. Manual error diagnostics retain the original error; observer failures do not change transaction behavior.
  • Add tenant-scoped SQL Server query() and getById(), full-precision cursors, exact binary text filters, and JSON/UTC normalization. Optional additive read indexes and read-only storage inspection are explicit installer/diagnostic operations; readers still need SELECT privileges.
  • Update runnable examples to 0.8.0 and add controlled PostgreSQL benchmark tooling. Candidate performance evidence has a defined local scope and does not establish SQL Server performance or a production SLO.
  • Separate optional soft-delete ecosystem validation from standalone publication. A supported combination still requires a compatible published peer and strict-peer lifecycle verification.

Release source · Manual transactions and validation · SQL Server · Upgrade guide

0.7.1 — 2026-10-25 ​

  • Raise the Node.js runtime requirement to ^22.23.4 || ^24.22.1. Update deployment runtimes and restart applications; changing the npm dependency does not update Node.js.
  • Add explicit provider: 'sqlserver' for manual AuditService.log(input, tx?) and schema utilities. PostgreSQL remains the default.
  • Add SQL Server flat-table storage with Unicode JSON text, UTC timestamps, JSON constraints, and UPDATE/DELETE rejection triggers. Unsupported provider operations fail before database access; SQL Server reads were added in 0.8.0.

Release source · Current SQL Server guide

0.7.0 — 2026-09-29 ​

  • Add defineAuditConfig() to keep module and extension storage, masking, actor, and tenant policies consistent and produce matching table options for schema and partition utilities. The factory builds options; it does not create clients, apply schema, or register Nest providers.
  • Add opt-in actorRequired (default false), requiring a non-blank string actor ID for user and system actors. Atomic policy failures reject before mutation and prevent helper completion even when caught. Best-effort omits the audit row and reports the error; manual log() rejects before INSERT, with transaction rollback left to the caller.
  • Breaking: reject tracked createManyAndReturn and updateManyAndReturn in atomic-required before the business query, inside or outside withAuditTransaction(). Catching the policy error inside the helper still rolls back prior business and audit work. Intentional tracking exclusions remain unchanged.
  • Warn once per model/operation for unsupported returning bulk operations in best-effort. These still produce no automatic rows; business results and errors are preserved.
  • Fix ensurePartitions() by casting partition-existence results to text so Prisma can decode PostgreSQL regclass values.
  • Expand the incremental adoption example and consumer verification for manual transactions, tenant-scoped role changes, authorized history, masking, concurrent actor context, and rollback.

Release source · Run the example · Add to an existing app · Upgrade guide

0.6.0 — 2026-09-10 ​

  • Add opt-in actorExtractionStage: 'interceptor' to extract an authenticated actor after Nest Guards. Middleware extraction remains the default.
  • Validate nested tracked writes through untracked parent models and intermediate relations.
  • Remember atomic audit failures and reject transaction completion even if the callback catches the audit error.
  • Treat equal scan checkpoints (after === until) as a completed range without replay.
  • Add a runnable Prisma 7/NestJS Quick Start and packaged consumer documentation checks; replace obsolete benchmark claims with reproducible per-mode measurements and clarify retention and timestamp-tail limits.

Release source

0.5.0 ​

  • Breaking: removed the deprecated experimentalTxAudit private-routing option; migrate authoritative automatic tracking to atomic-required plus withAuditTransaction(), while explicit best-effort remains non-atomic
  • Breaking: dropped Node.js 20 and now requires Node.js 22.13+ within the 22.x line or Node.js 24.x
  • Added NestJS 12.0.1+ support while retaining NestJS 10/11 compatibility, with NestJS 12 and Prisma 5/6/7 peer-matrix coverage
  • Added a consumer-owned PostgreSQL ecosystem gate for the exact published tenancy, audit-log, and soft-delete tuple and the packed audit-log candidate
  • Promoted atomic-required automatic tracking through withAuditTransaction() from Preview to Supported after the coordinated tenancy 0.15.0, audit-log 0.5.0, and soft-delete 0.7.1 PostgreSQL release gate
  • Upgraded the repository lint gate from ESLint 9 to ESLint 10
  • Updated CI and release workflows to Node.js 24-based GitHub Actions and retained npm provenance publishing
  • Isolated AuditStreamRunner observability hooks from delivery control flow: synchronous throws, rejected thenables, and mutation of reported errors no longer alter retry, DLQ, or checkpoint semantics; completed retry backoffs also remove their abort listeners
  • Resolved the installed NestJS major without importing the private @nestjs/core/package.json subpath, which is unavailable under NestJS 12 package exports
  • Preserved the original database failure as the error cause when partition pruning fails
  • See the v0.5.0 release and full comparison

0.4.1 ​

  • Added getAuditCapabilities() so cross-package lifecycle integrations fail closed unless the client advertises atomic-required consistency and atomic lifecycle support
  • Scoped lifecycle suppression to the matching outer delete operation and removed failed callback tokens, preventing one caught lifecycle failure from suppressing a later physical-delete audit
  • Rejected withAuditLifecycle() on best-effort clients before invoking the lifecycle callback
  • See the v0.4.1 release and full comparison

0.4.0 ​

  • Breaking: AuditExtensionOptions.consistency is required; select atomic-required or explicitly opt into legacy best-effort
  • Added createAuditedClient() and typed withAuditTransaction() so tracked writes, pre/post reads, and audit inserts commit or roll back in one official Prisma interactive transaction
  • Added row-locked single-record diffs, bounded record-level atomic deleteMany, mapped database identifiers, nested-write safeguards, and the audit-side withAuditLifecycle() bridge
  • Added AuditService.scan() with resumable checkpoints, a fixed high-watermark, bounded batches, tenant-explicit scope, filters, and cancellation
  • Added backpressure-aware AuditService.exportCsv() with a versioned CSV schema, canonical JSON, RFC 4180 records, and spreadsheet formula-injection defense
  • Added host-scheduled AuditStreamRunner, persistent PostgreSQL checkpoints/DLQ, HTTP and object-storage sinks, Datadog/Splunk mappings, bounded retries, metrics, and at-least-once delivery
  • Added retention checkpoint guards, recursive sensitive-key redaction, stricter input validation, and database-hardening guidance
  • Compatibility at the time of this release: the then-published @nestarc/soft-delete 0.6.0 did not expose the matching lifecycle options, so applications used its event/manual transaction path until 0.7.0 became available
  • See the v0.4.0 release and full comparison

0.3.0 ​

  • Added Prisma 7.9 primary development and CI coverage with Prisma Config, generated client output, and the PostgreSQL driver adapter
  • Retained declared Prisma 5/6 peer compatibility and raised the minimum Node.js version to 20.19
  • Fixed Prisma 7 driver-adapter deserialization in partition setup and pruning by casting PostgreSQL catalog relkind values to text
  • Clarified that automatic auditing in array $transaction([...]) calls is best-effort and can leave an orphan success row when the batch rolls back

0.2.0 ​

  • Breaking: createAuditExtension({}) now audits all Prisma models by default; set trackedModels or ignoredModels explicitly to narrow scope
  • Breaking: trackedModels: [] now audits no models, even when ignoredModels is also set
  • Added onAuditError, logger, logFailures, ignoreTimestampOnlyUpdates, tenantResolver, sensitiveFieldsByModel, and custom prismaModule options
  • Added async actor extraction, route exclusions, correlation ID metadata, public AuditInterceptor / AuditActorMiddleware exports, and @AuditReason()
  • Added dynamic audit table SQL with schema-qualified table names, trigger append-only enforcement, optional GIN indexes, monthly partitions, and ensurePartitions()
  • Added AuditService.prune() for flat-table and partitioned retention maintenance
  • Added Query API v2 with deterministic keyset cursors, optional totals, getById(), explicit tenantId, and allTenants admin reads
  • Documented the transaction contract: automatic audit inserts are best-effort outside caller transactions unless experimentalTxAudit is enabled
  • Fixed primary-key projection handling, wildcard escaping, audit pre-read failure handling, and Nest 11 middleware wildcard warnings

0.1.0 ​

  • Initial release
  • Automatic CUD tracking via Prisma $extends
  • Before/after diffs with deep JSON comparison
  • Sensitive field masking
  • Manual logging API with transaction support
  • Query API with wildcard filters
  • @NoAudit() / @AuditAction() decorators
  • Append-only PostgreSQL storage
  • Multi-tenant integration with @nestarc/tenancy

@nestarc/feature-flag ​

0.6.0 — 2026-09-10 ​

  • Add repository and tenantContextProvider options to synchronous/asynchronous registration; only the default repository needs a Prisma client instance, while the declared @prisma/client peer still applies.
  • Preserve explicit targetingKey, apply registry bucketing to typed/bulk evaluation, and add invocation/Admin bucketBy. Review existing rollout cohorts because formerly ignored inputs now affect decisions.
  • Reject null/fractional percentages and provide an SDK-compatible Boolean OpenFeature provider; other flag value types remain unsupported.
  • No database migration is required from 0.5.0. Use module options for custom providers and install the optional OpenFeature SDK when consuming its public types.

Release source · Upgrade guidance

0.5.0 ​

  • Moved the package to Prisma 7 as its supported Prisma major
  • Updated generation to the prisma-client generator with explicit output and moved CLI connection configuration to prisma.config.ts
  • Updated PostgreSQL tests, benchmarks, and examples to use @prisma/adapter-pg
  • Raised the Node.js requirement to 20.19+, 22.12+, or 24+
  • No database migration is required for this release

0.4.0 ​

  • Added detailed evaluateBoolean() results, invocation and guard fallbacks, explicit rollout targeting keys, and type-safe flag registries
  • Added opt-in exposure events, richer mutation metadata, test registry helpers, and a boolean OpenFeature provider
  • Kept the legacy rollout bucket fallback when no explicit targeting key or bucket field is configured

0.3.0 ​

0.2.0 ​

  • Pluggable cache adapters — CacheAdapter interface with MemoryCacheAdapter (default) and RedisCacheAdapter
  • Redis Pub/Sub — cross-instance cache invalidation via SCAN-based flush
  • Admin REST API — FeatureFlagAdminModule with mandatory guard injection (7 endpoints)
  • Repository pattern — FeatureFlagRepository interface with PrismaFeatureFlagRepository default
  • Tenant context provider — TenantContextProvider interface with automatic @nestarc/tenancy integration
  • findByKey() and removeOverride() methods on FeatureFlagService
  • All cache operations are now async (CacheAdapter interface)
  • cacheAdapter option added to FeatureFlagModuleOptions
  • setOverride() throws NotFoundException instead of generic Error
  • Admin endpoints return proper 404/409 status codes instead of 500
  • Override race conditions resolved (concurrent set/delete no longer 500)

0.1.0 ​

  • Initial release
  • Database-backed feature flags
  • @FeatureFlag() guard decorator
  • @BypassFeatureFlag() decorator
  • Percentage rollouts with murmurhash3
  • Tenant / user / environment overrides
  • 6-layer evaluation cascade
  • Built-in caching with TTL
  • Event system via @nestjs/event-emitter
  • TestFeatureFlagModule for testing

@nestarc/soft-delete ​

0.7.6 — 2026-11-15 ​

  • Add ^0.8.0 to the optional audit-log peer range while retaining all previous audit-log, tenancy, NestJS, Prisma, and standalone Node.js ranges. The schema and atomic lifecycle protocol are unchanged.
  • Document tenancy 0.16.4's public transaction callback with a dedicated audit-log → soft-delete client, explicit tenant resolution, aligned batch limits, and the same client injected into NestJS restore/purge services.
  • Validate exact package versions, engine and peer ranges, and artifact integrity without peer bypasses. Keep the audit-log 0.4.1 / tenancy 0.15.0 development baseline alongside the latest composition.
  • Verify the latest composition on Node.js 22.23.4/24.22.1 and Prisma 6.19.3/7.10.1. Packed PostgreSQL tests cover restricted-role RLS isolation, concurrent tenants, restore and permanent deletion, and rollback after user or audit failures.
  • Correct Quick Start provider exports, extended-client injection, and generated model types. Update lifecycle error guidance to describe audit-log before soft-delete inside the audit transaction owner.

Release source · Compatibility and setup · PostgreSQL validation

0.7.5 — 2026-10-29 ​

  • Share service classes, injection tokens, event emitters, and query context between root and /testing imports within the same module format (CommonJS or ESM).
  • Configure TestSoftDeleteModule with the production cascade provider, including the same explicit DMMF requirement.
  • Gate releases on installed tarball consumer tests for CJS/ESM loading, DI, query context, cascade restore, and strict public types. Database schema and peer ranges are unchanged.

Release source · Testing guide

0.7.4 — 2026-09-29 ​

  • Expand the optional audit-log peer range to include ^0.7.0; use soft-delete 0.7.4 with the site's audit-log 0.7.0 examples.
  • Preserve the existing atomic lifecycle handshake and runtime behavior; schema and extension APIs are unchanged.

Release source

0.7.3 — 2026-09-10 ​

  • Expand the optional audit-log peer range to include ^0.6.0, retaining existing atomic lifecycle capability checks.

0.7.2 — 2026-08-30 ​

  • Expand the optional tenancy peer to ^0.15.0 || ^0.16.0, verified with strict packed installs and PostgreSQL composition on Node 22.13/24.
  • The atomic audit lifecycle contract remains unchanged; installations composed with tenancy 0.16 inherit its newer Node requirement.

Release source

0.7.1 ​

  • Extended the optional @nestarc/audit-log peer range to ^0.4.1 || ^0.5.0; both lines use the same fail-closed atomic lifecycle capability handshake, with no soft-delete runtime behavior change

0.7.0 ​

  • Added opt-in auditLifecycle: 'atomic-required' integration with @nestarc/audit-log, using the fixed tenancy → audit-log → soft-delete extension order and withAuditTransaction()
  • Added deterministic Model.softDeleted, Model.restored, and Model.purged audit actions with record-level cascade and bulk metadata
  • Added the fail-closed auditMaxBatchRecords cap for atomic deleteMany and restoreMany conversion
  • Added PostgreSQL cross-package coverage for commit, rollback, repeated operations, restore, purge, cascade, bulk mutation, cap overflow, and tenant metadata against audit-log 0.4.1 and tenancy 0.15.0
  • Added real optional peer contracts for audit-log, tenancy, and event-emitter integrations
  • Hardened repeated and concurrent lifecycle mutations so state, relation, timestamp, and custom-primary-key predicates fail closed instead of emitting misleading evidence

0.6.0 ​

  • Added Prisma 7 to the peer range and made it the primary generated-client and PostgreSQL E2E target
  • Updated Prisma 7 setup to use Prisma Config, explicit generated output, and the PostgreSQL driver adapter
  • Shared extensions now import from @prisma/client/extension
  • Breaking for cascade/relation filtering setup: pass explicit dmmf metadata instead of relying on generated-client runtime metadata

0.5.0 ​

  • Added opt-in active-only filtering for to-many Prisma include and select trees
  • Added @WithDeletedRelations(...paths) for exact relation-path exceptions
  • Added SoftDeleteService.restoreMany() with cascade restore and optional event counts
  • Added PostgreSQL, SQLite, and MySQL recipes for uniqueness among active rows
  • Added NestJS 10 + Prisma 5 and NestJS 11 + Prisma 6 compatibility coverage
  • Fixed deleteMany() so already soft-deleted rows keep their original deletion timestamp
  • Added lint and package-content verification to the release workflow

0.4.0 ​

  • Stability release with PostgreSQL-backed E2E coverage for cascade soft-delete, cascade restore, purge, lifecycle events, and full NestJS HTTP integration
  • Fixed cascade restore so nested soft-deleted descendants restore through a withDeleted context
  • Hardened NestJS DI metadata for interceptor and optional event emitter injection
  • Release workflow now runs PostgreSQL E2E before npm publish
  • Excludes dist/.tsbuildinfo from the npm package

0.3.0 ​

  • Added explicit dmmf configuration for runtimes that do not expose Prisma.dmmf
  • Added CascadeDmmfMissingError
  • Fixed cascade setup so missing DMMF fails early instead of silently disabling cascade

0.2.0 ​

  • Cascade soft-delete and restore
  • forceDelete() for hard deletes
  • purge() with scheduled cleanup
  • Standalone createPrismaSoftDeleteExtension

0.1.0 ​

  • Initial release
  • Automatic soft-delete via Prisma extension
  • Transparent query filtering
  • @WithDeleted(), @OnlyDeleted(), @SkipSoftDelete() decorators
  • Actor tracking (deletedByField)
  • Lifecycle events

@nestarc/pagination ​

0.3.2 — 2026-10-27 ​

  • Count-free offset pagination fetches one extra matching row to determine links.next, while returning no more than the requested limit.
  • links.last is null when totals are unknown, including terminal and empty pages. Handle the public string | null response type before rendering a last-page link.
  • countStrategy: 'none' omits totals and runs neither the delegate count nor a custom count query. Exact and custom count behavior is unchanged.

Release source · Upgrade guidance · Pagination comparison

0.3.1 — 2026-10-27 ​

  • Fix keyset before navigation across deep pages and tied sort values, preserving the requested output order.
  • Count the complete filtered result set for exact/custom keyset totals, independently of the cursor boundary.
  • Include all effective sort fields in generated cursors, including fields fetched internally when omitted by select.
  • Apply module-level withTotalCount through PaginateService; endpoint settings retain precedence. Sending both after and before now returns HTTP 400.

Release source

0.3.0 ​

  • Added Prisma 7 generated-client type verification and PostgreSQL offset/cursor smoke tests in CI
  • Made Prisma 7 the primary development target while retaining Prisma 5/6 peer compatibility
  • Updated standalone Prisma setup to use Prisma Config, an explicit generated client, and the PostgreSQL driver adapter
  • Reran performance measurements with Prisma 7.9.1 and PostgreSQL 16

0.2.0 ​

  • Added stable keyset cursors for non-unique sort columns with tie-breaker columns
  • Added exact, omitted, and custom count strategies
  • Added endpoint-aware Swagger query documentation and withDeleted query pass-through

0.1.0 ​

  • Initial release
  • Offset + cursor pagination
  • 12 filter operators
  • Multi-column sorting with null positioning
  • Full-text search
  • Column/operator whitelisting
  • Swagger auto-documentation
  • Standalone paginate() function
  • TestPaginationModule for testing

@nestarc/idempotency ​

1.0.0 — 2026-10-07 ​

  • Breaking: require Node.js 22 or 24. Import Redis and PostgreSQL adapters from /redis and /postgres; memory-only imports no longer require optional drivers.
  • Breaking: use versioned hashed storage keys and opaque response bodies. Move to a separate empty namespace, stop old/new process overlap, preserve durable business deduplication, and reconcile outstanding work across migration and rollback. No SQL schema change is required from 0.4.
  • Custom scopes add identity components to the endpoint instead of replacing endpoint isolation. Validate raw/repeated header keys and count UTF-8 bytes in maxKeyLength.
  • Replace raw scope/error telemetry with hashed namespace, keyHash, and fixed error classifications. Hashes are not anonymity guarantees or suitable metric labels.
  • Capture only the final completed HTTP Observable value; reject direct manual responses, redirects, rendering, and SSE before execution. Unsupported response capture retains its processing lease.
  • Enforce ownership and expiration on completion, preserve ambiguous successful writes after completion failures, and support long TTLs without stale timer deletion.
  • Add executable adoption/migration examples, installed-tarball consumer gates, and real Redis/PostgreSQL verification across supported combinations.

Release source · Migration and rollback

0.4.0 ​

  • Added processingTtl for separate in-flight PROCESSING leases and completed replay TTLs
  • Added keyResolver, maxKeyLength, and custom fingerprint resolvers for webhook event ids, command ids, and semantic request fingerprints
  • Added observability.onEvent, Idempotency-Status, and Idempotency-Replayed response headers
  • Exported PostgresStorage from the storage barrel
  • Clarified draft-07-compatible behavior and the HTTP-boundary guarantee

0.3.0 ​

  • Stable JSON request fingerprinting so object key order does not cause false 422 responses
  • Safe response header capture and replay for Content-Type, Location, ETag, Cache-Control, and X-* headers
  • Fastify adapter E2E verification
  • Real Redis smoke coverage in CI
  • Default endpoint scoping now uses the actual request path without query string
  • Postgres migration: add response_headers JSONB to existing idempotency records

0.1.3 ​

  • Token-based compare-and-set for TTL-expiry race prevention
  • Per-endpoint key scoping via PATH_METADATA (HTTP_METHOD /route:: prefix)
  • TTL boundary validation (positive integer only)
  • Concurrent duplicate regression coverage
  • Transient storage.complete() failure no longer causes duplicate execution

0.1.0 ​

  • Initial release
  • IETF httpapi-idempotency-key-header-07 state machine (400 / 409 / 422)
  • @Idempotent() decorator with per-handler overrides
  • IdempotencyInterceptor with opt-in wiring (global / controller / method)
  • MemoryStorage and RedisStorage adapters
  • SHA-256 request body fingerprint
  • Response replay (status code + body)
  • Configurable scope (endpoint / global / custom function)
  • Binary response detection and bypass

@nestarc/outbox ​

0.4.1 — 2026-10-31 ​

  • Export OutboxPoller from the root and both module registrations, with stop({ timeoutMs }) to fence new claims and await publishing, heartbeats and fenced DB completion before closing Jobs.
  • Export OutboxStopOptions, OutboxShutdownError, and OUTBOX_SHUTDOWN_INCOMPLETE. Incomplete automatic drain now rejects instead of logging and returning; keep callback dependencies open on timeout and retry after settlement.
  • Prevent polling from restarting after stop and release claims acquired during stop without consuming retry budget. No SQL migration is needed from the current 0.3 schema.

Release source · Shutdown guide

0.4.0 — 2026-09-11 ​

  • Breaking: polling.enabled: false now fails setup, even with LISTEN/NOTIFY. Periodic polling remains required for backlog, retries, and expired claims.
  • Breaking: version 2 admin cursors preserve PostgreSQL microseconds; restart traversals because version 1 cursors are rejected.
  • Validate tenant/provider/callback/notification configuration at setup and retain application-owned shutdown hooks with a 30-second drain bound.
  • Keep schema version 0.3.0; current 0.3 installations need no additional SQL migration. Ship runnable and packed consumer examples.

Release source · Installation and migration

0.3.0 — 2026-09-05 ​

  • Breaking: move to Node 22/24, drain old pollers, and apply upgrade-to-current.sql before deployment. Startup checks the required schema with OUTBOX_SCHEMA_MISMATCH diagnostics.
  • Claim one record on demand using renewable PostgreSQL leases and fenced completion; persist retry eligibility in next_attempt_at with bounded retry.maxDelay.
  • Add privileged OutboxOperatorService, fixed tenant admin scopes, cursor pagination, and structured compare-and-set mutation outcomes.
  • Add tenant provenance policies and explicit tenantScope: 'global'; reject invalid envelopes before SQL and prevalidate/chunk bulk inserts.
  • Move async transport/provider registrations outside factory results; expose only root APIs and documented fresh/current SQL paths.
  • Coalesce polling/notification/manual triggers, recover listener connections with capped backoff, and isolate callback snapshots. Delivery remains at-least-once with no FIFO or downstream-completion guarantee.
  • Support NestJS 12 with Schedule 12 and retain NestJS 10/11 plus Prisma 5/6/7 consumer coverage.

Release source · Migration

0.2.1 — 2026-08-30 ​

  • Add Prisma 7 peers and a driver-adapter E2E path, retain Prisma 6, and verify the strict packed NestJS 11/Prisma 7 consumer.

0.1.0 ​

  • Initial release
  • Prisma-native transactional outbox table and SQL migration
  • Polling with FOR UPDATE SKIP LOCKED for multi-replica safety
  • @OnOutboxEvent() decorator and type-safe event classes
  • Fixed and exponential retry backoff strategies
  • Stuck event recovery and graceful shutdown
  • Local transport plus custom transport adapter support

@nestarc/inbox ​

0.2.0 — 2026-10-28 ​

  • Add @nestarc/inbox/testing with drainInbox(), waitForInboxRecord(), and typed InboxTestError diagnostics. Use the real Inbox service and scoped admin view with a timeout, cancellation signal, and pass limit. Receipt IDs select assertions, not worker claims; timeouts do not cancel transactions already in flight.
  • Keep runtime processing contracts and SQL schema v2 unchanged. Existing 0.1.0 installations need no database migration. Peer dependencies and the site's Preview classification remain unchanged.
  • Add recovery checks for TCP disconnects and blackholes, pool pressure, real SIGTERM shutdown, PostgreSQL standby promotion after confirmed WAL replay, bounded business-tablespace ENOSPC, and RabbitMQ restart, retry, and dead-letter handling.
  • Record two disk-backed local runs with concurrent ingress, processing, pool pressure, hot/cold tenant latency, retry recovery, and retention measurements. These several-minute Docker VM observations do not establish production capacity, tenant fairness, or an SLA.
  • Gate releases on operational recovery checks and allow up to 20 minutes for npm post-publication scanning before verifying registry integrity.

Follow handler testing, upgrade and schema setup, and operations. See the 0.2.0 release and versioned validation record for the upstream evidence.

0.1.0 — 2026-10-28 ​

  • First public release of a transactional inbox for NestJS, Prisma, and PostgreSQL, with SQL schema v2. The site classifies this pre-1.0 API as Preview; review schema and API changes before upgrades.
  • Deduplicate retained identities composed of scope, source, consumer, and message ID. Matching content returns duplicate; changed content raises InboxConflictError.
  • Store receipts before transport acknowledgment, then commit handler writes through context.tx, optional outbox writes, and receipt completion in one database transaction.
  • Recover eligible work with PostgreSQL leases, claim tokens, persisted retry timing, and bounded workers. Inspect DEAD records, requeue failures, or explicitly replay completed messages with a new receipt and audit lineage.
  • Require NestJS ^11.2.8, Prisma ^7.10.1, and Node.js >=22.12.0; PostgreSQL 16 and 18 are the recorded validation targets. Optional tenancy uses @nestarc/tenancy ^0.16.2. Use patched Node 22.23.4+ or 24.22.1+ to match the validation and tenancy examples.
  • Apply the installation SQL before startup; runtime validates the schema without creating it. Local schema v1 users need the packaged v1-to-v2 migration. External side effects, message ordering, and identities removed by retention remain outside the atomic database guarantee.

Start with Inbox installation, processing boundaries, and operations. See the 0.1.0 release for the original publication record.


@nestarc/webhook ​

0.13.3 — 2026-10-29 ​

  • Return the original signing key from endpoint creation when using an encrypting WebhookSecretVault, for generated and explicit keys.
  • Keep persisted keys and queued signing snapshots encrypted, and keep secrets omitted from read responses.
  • Add real PostgreSQL encrypted-vault delivery coverage and installed consumer regression checks. Tenant filters, delivery transactions, and the 0.13 schema are unchanged.

Release source · Provisioning and vaults

0.13.2 — 2026-09-11 ​

  • Persist correlationId independently of idempotencyKey and pass correlation metadata to custom event repositories.
  • Use the configured delivery.maxRetries total attempt budget for replay instead of always using five attempts.
  • Reject individual/bulk retries for purged events and serialize retry, replay, and retention through event-row locks.
  • Export WebhookHttpClientRequestOptions for custom HTTP adapters and add a packed Prisma 7 consumer with raw-body verification and receiver deduplication.

Release source · Installation

0.13.1 — 2026-08-30 ​

  • Add Prisma 7 support to the default PostgreSQL repositories and verify the exact NestJS 11.2.1/Prisma 7.10.0 packed consumer.
  • Retain the independent Prisma 6.19.3 legacy database lane.
  • Fix retention purge queries by casting cutoff parameters to timestamptz for the Prisma 7 PostgreSQL adapter.

Release source

0.13.0 ​

  • Added idempotent event publishing with optional correlation IDs
  • Added bounded bulk retry and event replay administration APIs
  • Added worker concurrency, backlog draining, observer callbacks, and backlog diagnostics
  • Added payload/response redaction hooks and configurable retention purge operations
  • Added timestamp-tolerant signature verification and completed the secret-rotation overlap workflow

0.12.1 ​

  • Fixed successful-delivery circuit-breaker resets to avoid rewriting already-healthy endpoint rows
  • Reduced webhook_endpoints row-lock contention during high-throughput worker scale-out

0.2.0 ​

  • Outbound webhook delivery with endpoint, event, and delivery tables
  • HMAC-SHA256 signatures using Standard Webhooks-compatible headers
  • Exponential retry schedule with jitter and circuit breaker support
  • Dead letter queue and full delivery-attempt logs
  • Multi-instance safe polling with FOR UPDATE SKIP LOCKED
  • SSRF defenses for endpoint registration and dispatch
  • Ports/adapters architecture for Prisma and fetch customization

@nestarc/api-keys ​

0.4.0 — 2026-08-31 ​

  • Add authorizeRequest() for environment/IP/scope authorization; guard denials no longer touch usage timestamps or emit successful usage events.
  • Add tenant-bound revoke/rotate operations, atomic one-winner rotation, and an exported framework-independent storage contract runner.
  • Return safe ApiKeySummary[] management lists; validate namespace, scope, tenant, time, and expiration inputs before mutation.
  • Authenticate secrets before exposing lifecycle state, bind the raw environment segment to stored identity, and isolate observer/context-writer mutations.
  • Add separate authorization-denial and prefix-collision metrics; ApiKeyError now extends Nest HttpException with a safe status/code response.
  • Breaking: require Node ^22.13.0 || ^24.0.0 and TypeScript 5.3+, use root imports, and migrate custom rotate() adapters to atomic 'rotated' | 'not_rotatable' results.
  • Support NestJS 10/11/12 with Prisma 5/6/7 storage verification and a Prisma-free custom/in-memory path.

Release source · Upgrade checklist

0.3.2 — 2026-08-30 ​

  • Add Prisma 7 PostgreSQL storage support, NestJS 11 peers, and packaged legacy/Prisma 7 schema and config examples with strict consumer verification.

0.3.1 ​

  • Expanded the optional @prisma/client peer range to ^5.0.0 || ^6.0.0
  • Added real PostgreSQL storage-contract coverage for CRUD, tenant isolation, field mapping, rotation, and transaction rollback
  • Added matching Prisma 5.22.0 and 6.19.3 pre-release verification plus a strict tarball consumer install on Prisma 6

0.3.0 ​

  • Added per-key IPv4, IPv6, and CIDR allowlists through allowedIpCidrs
  • Added an injectable clientIpResolver; restricted keys fail closed when a valid client IP cannot be resolved
  • Added low-cardinality api_key.verification metrics through onMetric, with isolated sink failure reporting through onMetricError
  • Added createTestKey() for consumer integration tests
  • Added compatibility coverage and guidance for @nestarc/rbac API-key subject resolution
  • Updated the Prisma example with allowedIpCidrs String[] @default([]) and restored the benchmark smoke check in CI

0.2.0 ​

  • Added zero-downtime user key replacement through ApiKeysService.rotate() and rotation metadata
  • Added lifecycle hooks for create, revoke, rotate, authentication failure, and opt-in usage events
  • Added TTL policy controls for default expiry, maximum expiry, and disallowing non-expiring keys
  • Added @CurrentApiKey(), getApiKeyContext(), contextWriter, and a safe key prefix in the request context
  • Extended the storage contract with findById() and atomic rotate() support

0.1.0 ​

  • Initial release
  • Stripe-style key format with indexable prefixes
  • SHA-256 hashing with versioned pepper rotation
  • Live/test environment isolation
  • Scope guards and tenant-scoped key context

@nestarc/rbac ​

0.2.2 — 2026-09-02 ​

  • Reconcile populated user, RBAC subject, API-key, and tenant sources; conflicting identities fail closed. request.apiKey is canonical and configured tenant resolvers are authoritative by default.
  • Make stacked guard audit events reflect the final RBAC request decision and emit mutation success events only for committed changes in capable adapters.
  • Add producer-specific service decision types, optional mutation results, and indexed role lookup for strict assignment. updateRole() no longer creates missing roles.
  • Validate runtime modes and records, preserve exact API-key identities, document HTTP-only guards and transport-neutral service checks, and deprecate legacy resolver/custom-storage fallbacks.
  • Expand NestJS peers through 12 with strict NestJS 10/11/12 and Prisma 5/6/7 evidence on Node 22/24.

Release source

0.2.1 — 2026-08-30 ​

  • Add Prisma 7 driver-adapter support, retain Prisma 6 regression coverage, and verify the packed NestJS 11/Prisma 7 consumer.

0.2.0 ​

  • Added defineRbacPermissions() for typed permission contracts without changing persisted string values
  • Added createStrictRbacOptions() for fail-closed metadata, tenant, storage-error, and write-validation defaults
  • Added safe optional RbacDecision.details for server-side decision tracing
  • Added policy-change publisher hooks for successful role, permission, and binding mutations
  • Added @nestarc/rbac/integrations/audit-log with secret-shaped metadata sanitization
  • Added expectDeniedReason(), createRbacScenario(), and expectRbacMatrix() testing helpers
  • Kept the 0.1 Prisma schema and string-permission APIs compatible

0.1.0 ​

  • Initial public release of tenant-aware RBAC primitives for NestJS SaaS applications
  • Optional Prisma/PostgreSQL persistence through @nestarc/rbac/prisma
  • PrismaRbacStorage implementation of the RbacStorage contract
  • Prisma schema example and initial RBAC SQL migration for consuming applications
  • Public testing helpers through @nestarc/rbac/testing
  • Optional integration helpers for @nestarc/tenancy and @nestarc/api-keys
  • Audit event emission for RBAC write operations and denied guard decisions
  • tenant.allowGlobalRolesInTenant support for explicit global-role opt-in
  • Multi-entry ESM, CJS, and type declaration output
  • Documentation for installation, guards, Prisma setup, testing utilities, and integrations

@nestarc/mcp-guard ​

Labs tooling

@nestarc/mcp-guard is published under the @nestarc npm scope, but it is separate from the NestJS SaaS package lineup.

0.2.0 ​

  • Discovery mode for Cursor, VS Code, Claude Code, and Claude Desktop MCP config locations
  • Discovery options: --client, --scope, and --list-targets
  • Aggregate JSON schema v2 and grouped text output
  • Server normalization now preserves headers, envFile, and type fields
  • MCPG001 scans secret-like header keys as well as environment variables

@nestarc/data-subject ​

0.3.0 — 2026-10-11 ​

  • Breaking: export includes only explicit exportFields; omitted or empty allowlists exclude the entity. Prisma executors require tenantField or an explicit matching singleTenantId, and request lookup/update now require tenant ID.
  • Breaking: erasure requires stable scalar identity and selectByIds verification by default. Shared definePolicy() definitions align runtime and lint; evidence v2 records policy hashes, actual strategies, and field verification results.
  • Add signed read-only erasure previews with expiry and transaction-bound policy/scope revalidation.
  • Add optional PrismaExecutionStore for durable idempotency, atomic data/request/outbox persistence, and original-byte artifact and notification recovery. Apply its model and migration before enabling it.
  • Add an optional PostgreSQL queue with atomic page checkpoints, bounded NDJSON export, retry limits, cancellation, and partial completion. Earlier committed batches remain committed after later failure or cancellation.
  • Add a Transcend erasure adapter and private S3 reference implementation, with separate local/provider outcomes and artifact retention. These paths have synthetic verification; live provider and customer workload validation remain separate.
  • Fix BigInt export serialization, DateTime/Decimal/BigInt replacement verification, composite-relation lint, and native .mjs CLI configuration loading.
  • Declare NestJS ^10.0.0 || ^11.2.7 and optional Prisma ^5.0.0 || ^7.10.0 peers; Prisma 6 is not included. PostgreSQL consumer profiles verify Nest 10/Prisma 5 and Nest 11/Prisma 7.

Release source · Migration guide · Execution and recovery

0.2.0 — 2026-06-19 ​

  • Add persistent request records through PrismaRequestStorage, stable artifact keys, erasure evidence JSON with pre/post-scan statistics, and full audit lifecycle events.
  • Add the Prisma schema/policy lint CLI and runtime registry validation; normalize failure reasons and omit raw rows and field values from evidence.

Release source

0.1.0 ​

  • Initial release
  • Declarative entity registry for export and erase policies
  • DataSubjectService lifecycle for request lookup, export, and erase
  • Delete, anonymize, retain, and mixed strategies per field
  • Legal retention support with explicit basis and retention windows
  • Prisma executor plus in-memory request and artifact stores
  • Outbox-style event publisher integration

@nestarc/jobs ​

0.4.2 — 2026-10-31 ​

  • Accept optional Outbox ^0.4.0 while retaining ^0.2.1 || ^0.3.0, and expose optional OutboxRecord.nextAttemptAt.
  • Verify packed PostgreSQL/Redis consumers with Outbox 0.4.1 across Node 22/24 and Nest 10/11, including rollback, process loss after enqueue, deduplication, tenant isolation, lineage, active drain, timeout/retry and restart.
  • Document Outbox stop-before-Jobs-close ordering. Release verification now waits for npm metadata and tarball visibility while retaining integrity, signature and provenance requirements.

Release source · Latest Outbox integration

0.4.1 — 2026-10-29 ​

  • Correct the npm README's stale publication status and planned-feature wording to describe the released 0.4 contracts.
  • Pin compatible setup examples to Jobs 0.4.1, BullMQ ^5.76.2, and Outbox 0.3.0. Runtime APIs and peer ranges are unchanged.

Release source · Installation

0.4.0 — 2026-09-05 ​

  • Add BullMQ producer, worker, and both roles, bootstrap handler validation, tenant-filtered status reads, worker error observers, and explicit terminal-retention cleanup.
  • Run in-memory work in a bounded pool (default 10) with module-wide tenant limits and per-type caps; use poolSize: 1 for prior serial behavior.
  • Validate options before identity reservation and normalize portable JSON values. Custom backend completions now require activation fencing.
  • Keep timed-out handlers owned until settlement; close in-memory admission before draining accepted work and report incomplete shutdown with JobsShutdownError.
  • Fake drains now reject exhausted iteration budgets with jobs_drain_limit_exceeded; history snapshots are detached.
  • Default first-party outbox dedupe to tenant scope when a tenant exists; preserve canonical source lineage despite mapping callback mutation. Deprecate JobsOutboxBridge.
  • Support Node 22/24; raise optional peers to BullMQ ^5.76.2 and Outbox ^0.2.1 || ^0.3.0. Source-poller shutdown still requires explicit orchestration.

Release source · Upgrade guide

0.3.1 ​

  • Deferred @JobHandler() discovery until application bootstrap, after provider construction and onModuleInit() hooks complete
  • Started in-memory and BullMQ consumers only after handler registration, so work queued before app.init() waits for initialized handlers
  • Made request/transient-scoped handlers and singleton handlers with non-static dependency trees fail explicitly during bootstrap

0.3.0 ​

  • Added createOutboxJobsPublisher() for first-party @nestarc/outbox integration, preserving tenant, correlation, causation, and event lineage while using the outbox record ID as stable job identity
  • Made BullMQ execution restart-safe by registering declared queues and persisting context, metadata, scheduledFor, backoff, idempotency, and dedupe lineage in Redis, with backward reads for queued 0.2 jobs
  • Added Redis-backed job-type idempotency and global/tenant dedupe, accurate created-vs-deduped results, capped exponential backoff with jitter, and graceful producer/worker shutdown
  • Hardened in-memory fairness, delayed work and retry ordering, DLQ replay state restoration, lifecycle event isolation, and mutation-isolated lifecycle snapshots
  • Aligned typed handlers with handle(payload, context), applied typed job defaults at runtime and in FakeJobsService, and added explicit jobs_capability_unsupported, jobs_backend_closed, and jobs_identity_conflict errors
  • Breaking for BullMQ upgrades: use a coordinated stop-and-restart cutover rather than mixed 0.2/0.3 workers, use a dot-free namespace, and require BullMQ ^5.74.1 with Node.js 20, 22, or 24 and NestJS 10 or 11
  • Compatibility: typed payloads and contexts must be plain objects, __nestarcJob is now reserved, generated idempotency job IDs are hashed, and unsupported BullMQ timeout/history/DLQ/manual-drain operations now fail explicitly

0.2.0 ​

  • Added typed job contracts with defineJobs(), job(), TypedJobsService, TypedJobHandler, JobInstance, and InjectJobs()
  • Added backend capability reporting plus normalized status and history APIs
  • Added in-memory retry, backoff, cooperative timeout, idempotency keys, tenant/global dedupe, and dead-letter list/replay/discard operations
  • Added enqueueDetailed() for distinguishing created and deduped enqueues, lifecycle event hooks, and deterministic delayed-job testing with createFakeJobs() and FakeClock
  • Preserved the 0.1 module, decorator, and string-based enqueue APIs
  • BullMQ remained standard FIFO without distributed tenant fairness or DLQ administration; timeout cancellation remained cooperative and could not stop synchronous CPU-bound handlers

0.1.0 ​

  • Initial release
  • In-memory backend with weighted tenant fairness and starvation protection
  • BullMQ backend for Redis-backed production workers
  • @JobHandler() provider discovery
  • Context propagation through pluggable extractors and runners
  • Outbox-to-jobs bridge
  • FakeJobsService for deterministic tests

Last updated:

Documentation site: MIT License. Check each package for its license.