Skip to content

v1.2.2

Latest

Choose a tag to compare

@github-actions github-actions released this 05 Oct 11:42
4d98054

@walq/core

Patch Changes

  • fd98379: Report malformed job JSON as onError operation parse instead of handler, with the same job ID, attempt, and attemptsExhausted fields. Handlers still receive only valid payloads, and retry/backoff behavior is unchanged in both process and processMany. Consumers switching on context.operation should handle the new parse operation.
  • e8af85e: Report unexpected worker polling failures and reject malformed grouped claim results instead of treating missing results as empty claims.
  • 946b1b6: Preserve the original error and context when onError fails, retain cron validation causes, and handle unexpected background rejections without letting logging failures disrupt polling. Public APIs and retry policies are unchanged.
  • e66742d: Document error logging, direct-call rejections, worker diagnostics, and aggregate cleanup errors.
  • 2fdd44c: Include error cause chains in persisted job.error diagnostic text. Formatting is depth-bounded, handles circular references, and does not invoke custom inspection hooks. Errors without causes keep their existing text; onError still receives the original error and retry behavior is unchanged.

@walq/sqlite-common

Patch Changes

  • 685303a: Use serialize-error for storage worker error transport so causes, SQLite diagnostic fields, and custom enumerable properties are preserved. Error properties are serialized with bounded depth and without invoking custom toJSON hooks. Public APIs and SQL execution policies are unchanged.
  • Updated dependencies [fd98379]
  • Updated dependencies [e8af85e]
  • Updated dependencies [946b1b6]
  • Updated dependencies [e66742d]
  • Updated dependencies [2fdd44c]
    • @walq/core@1.2.2

@walq/better-sqlite3

Patch Changes

  • b4fb895: Preserve both the original and cleanup errors when node:sqlite rollback fails or a managed adapter cannot close after initialization failure. These failures reject with a standard AggregateError containing both errors and the original as cause. Successful cleanup still rethrows the original error unchanged.
  • 685303a: Use serialize-error for storage worker error transport so causes, SQLite diagnostic fields, and custom enumerable properties are preserved. Error properties are serialized with bounded depth and without invoking custom toJSON hooks. Public APIs and SQL execution policies are unchanged.
  • e66742d: Document error logging, direct-call rejections, worker diagnostics, and aggregate cleanup errors.
  • Updated dependencies [fd98379]
  • Updated dependencies [e8af85e]
  • Updated dependencies [685303a]
  • Updated dependencies [946b1b6]
  • Updated dependencies [e66742d]
  • Updated dependencies [2fdd44c]
    • @walq/core@1.2.2
    • @walq/sqlite-common@1.2.2

@walq/sqlite

Patch Changes

  • b4fb895: Preserve both the original and cleanup errors when node:sqlite rollback fails or a managed adapter cannot close after initialization failure. These failures reject with a standard AggregateError containing both errors and the original as cause. Successful cleanup still rethrows the original error unchanged.
  • 685303a: Use serialize-error for storage worker error transport so causes, SQLite diagnostic fields, and custom enumerable properties are preserved. Error properties are serialized with bounded depth and without invoking custom toJSON hooks. Public APIs and SQL execution policies are unchanged.
  • e66742d: Document error logging, direct-call rejections, worker diagnostics, and aggregate cleanup errors.
  • Updated dependencies [fd98379]
  • Updated dependencies [e8af85e]
  • Updated dependencies [685303a]
  • Updated dependencies [946b1b6]
  • Updated dependencies [e66742d]
  • Updated dependencies [2fdd44c]
    • @walq/core@1.2.2
    • @walq/sqlite-common@1.2.2