Skip to content

duroxide-node 0.2.4

Latest
Latest

Choose a tag to compare

View all tags
@ChrisKrawczyk ChrisKrawczyk released this 28 Oct 18:53
v0.2.4
7722f19
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Changed

  • Require duroxide-pg 0.1.38 and adopt its PostgreSQL lock-safety fix.
  • Fix deadlocks between renewal and fetch, acknowledge, or abandon; prevent renewal from reviving an expired lease or shortening a live one; and reject acknowledge after another worker has taken over. Renewal retries transient errors.
  • No JavaScript API change.

Database upgrade notice

PostgreSQL connections apply migration 0026. It replaces the renewal and acknowledge procedures and adds a unique index on instance_locks(lock_token). The index is not built concurrently and blocks writes to that table while it builds. Check database upgrade and rollback compatibility before deployment: an older native build can reject a database containing an unknown migration.

Packages

The six npm-format tarballs attached here are unchanged copies of the production release artifacts used for the npm 0.2.4 publication: the duroxide wrapper and all five native platform packages. They are not separately rebuilt GitHub Actions binaries. SHA256SUMS records the SHA256 of each tarball.

Both GNU/Linux binaries have a highest required GLIBC symbol version of GLIBC_2.34; these are not the separate GitHub 0.2.3 Linux x64 build that required GLIBC_2.39.

This release uses the existing v0.2.4 tag at commit 7722f193184af0f2b01095b72464607b97d92aa1. No existing release assets are replaced.

Full changelog: v0.2.3...v0.2.4

Assets 9
Loading