Skip to content

Releases: pkcprotocol/node-proper-lockfile

v4.2.1

17 Apr 06:33

Choose a tag to compare

4.2.1 (2026-04-17)

Bug Fixes

  • use type-only import for type declarations (84295e4)

v4.2.0

17 Apr 06:15

Choose a tag to compare

4.2.0 (2026-04-17)

⚠ BREAKING CHANGES

  • We were marking the lock as compromised when system went into sleep or if the event loop was busy taking too long to run the internals timers, Now we keep track of the mtime updated by the current process, and if we lose some cycles in the update process but recover and the mtime is still ours we do not mark the lock as compromised.
  • remove callback support
  • use of node lts language features such as object spread
  • compromised function in lock() has been moved to an option

chore

  • update project to latest node lts (b1d43e5)

Features

  • add lock path option (#66) (32f1b8d)
  • add signal exit (#65) (f20bc45)
  • allow second precision in mtime comparison (#78) (b2816a6)
  • make staleness check more robust (#74) (9cc0973), closes #71
  • migrate to TypeScript, rename to @pkc/proper-lock-file, pin Node 20 (4c7e51a)

Bug Fixes

  • add prepare script so dist/ is built on git install (30564d7)
  • fix mtime precision on some filesystems (#88) (f266158), closes #82 #87
  • fix node 14 updating graceful-fs (#102) (b0d988e)
  • fix typo in error message (#68) (b91cb55)
  • package: change package name to @plebbit/node-proper-lockfile (7fd6332)
  • package: update retry to version 0.12.0 (#50) (d400b98)
  • restore ability to use lockfile() directly (0ef8fbc)
  • updated locks key to be filepath + lock file path (d8b6381)

Reverts

Build System

  • add automated versioning, npm trusted publishing, and GitHub Actions CI (eaabc97)