proper-lockfile changelog

Changelog History

Page 1

• v4.1.2 Changes

  January 25, 2021

  🐛 Bug Fixes

  • 🛠 fix node 14 updating graceful-fs (#102) (b0d988e)

• v4.1.1 Changes

  April 03, 2019

  🐛 Bug Fixes

  • 🛠 fix mtime precision on some filesystems (#88) (f266158), closes #82 #87

• v4.1.0 Changes

  March 18, 2019

  🔋 Features

  • 👍 allow second precision in mtime comparison (#78) (b2816a6)

• v4.0.0 Changes

  March 12, 2019

  🐛 Bug Fixes

  • 🛠 fix typo in error message (#68) (b91cb55)

  🔋 Features

  • 👉 make staleness check more robust (#74) (9cc0973), closes #71 /github.com/ipfs/js-ipfs-repo/issues/188#issuecomment-468682971

  💥 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.

• v3.2.0 Changes

  November 19, 2018

  🔋 Features

  • ➕ add lock path option (#66) (32f1b8d)

• v3.1.0 Changes

  November 15, 2018

  🐛 Bug Fixes

  • 📦 package: update retry to version 0.12.0 (#50) (d400b98)

  🔋 Features

  • ➕ add signal exit (#65) (f20bc45)

• v3.0.2 Changes

  January 30, 2018

• v3.0.1 Changes

  January 20, 2018

  🐛 Bug Fixes

  • ⏪ restore ability to use lockfile() directly (0ef8fbc)

• v3.0.0 Changes

  January 20, 2018

  Chores

  • ⚡️ update project to latest node lts (b1d43e5)

  💥 BREAKING CHANGES

  • ✂ remove callback support
  • 👉 use of node lts language features such as object spread
  • 🔒 compromised function in lock() has been moved to an option

• v2.0.1

  April 24, 2017

• 1
• 2
• Next ›
• Last »