v0.1.27

Release v0.1.27.

• Update to duroxide-pg 0.1.34 and adapt PostgreSQL provider initialization to the ProviderConfig API.
• Keep duroxide core at 0.1.29 and resolve dependencies from published registries.
• Refresh npm release metadata and platform package documentation, including the Windows package alias.

npm provenance note: npm duroxide@0.1.27 and platform packages were published by the trusted-publishing recovery workflow from main@9803f385580f94c09691666424d75de19ce4af5b after CI-only publish workflow fixes landed on top of this release tag. The original v0.1.27 tag remains unchanged; the non-rewriting npm-v0.1.27-provenance tag marks the exact source commit used by npm provenance.

v0.1.26

Pick up duroxide-pg 0.1.33 with native-tls fix (resolves TLS handshake failures in AAD token acquisition). See CHANGELOG.md for details.

v0.1.25

Release duroxide-node 0.1.25 with duroxide 0.1.29, duroxide-pg 0.1.32, and Microsoft Entra ID PostgreSQL provider constructors.

v0.1.24

Added

• Publish the new duroxide-linux-arm64-gnu native npm package for aarch64-unknown-linux-gnu.
• Add Linux ARM64 CI build, local smoke, publish verification, and registry smoke coverage on ubuntu-24.04-arm.

This release unblocks Linux ARM64 Node.js containers from importing duroxide.

v0.1.23

Fixed

• Windows packaging — index.js was regenerated by napi build during the 0.1.22 release and lost the manual require('duroxide-windows-x64') patch from #13, falling back to the (non-existent) napi-default name duroxide-win32-x64-msvc. Re-apply the fix.

Changed

• Bumped duroxide dependency — 0.1.27 → 0.1.28 (drops transitive ring crate via SQLx native-tls upstream)
• Bumped duroxide-pg dependency — 0.1.29 → 0.1.30 (same ring-drop cascade)

⚠️ Do not use 0.1.22 — it was tagged but never published due to the Windows packaging regression noted above. Use 0.1.23.

v0.1.22

Changed

• Bumped duroxide dependency — 0.1.27 → 0.1.28 (drops transitive ring crate via SQLx native-tls upstream)
• Bumped duroxide-pg dependency — 0.1.29 → 0.1.30 (same ring-drop cascade)
• No source code changes; pure dependency uplift

v0.1.21

Fixed

• npm install duroxide now correctly pulls the duroxide-windows-x64 optional dependency. In v0.1.20, napi-rs's prepublish step rewrote the published optionalDependencies back to the default duroxide-win32-x64-msvc name, which does not exist on npm post-rename — so Windows installs failed with MODULE_NOT_FOUND. Caught by the new post-publish registry smoke.

CI now publishes the main package with --ignore-scripts to preserve our manifest exactly. All platform-binary prep still happens in earlier workflow steps.

See CHANGELOG.md.

v0.1.20

Fixed

• Windows dispatcher now resolves the correct platform subpackage (duroxide-windows-x64). Previously require('duroxide-win32-x64-msvc') in index.js threw MODULE_NOT_FOUND, making duroxide@0.1.19 unusable on Windows (#13).

Added

• Cross-platform packaging smoke tests (ci/smoke/) that install from local tarballs on ubuntu, macos-14, macos-13, and windows-latest, plus post-publish registry smoke. Publish is gated on all-platform smoke success.

See CHANGELOG.md.

v0.1.19

Bump duroxide-pg 0.1.28 → 0.1.29 (migration race fix, microsoft/duroxide#10)

Fixed (via duroxide-pg 0.1.29)

• Migration race condition on concurrent worker startup — advisory lock now serializes migrations
• Cached plan invalidation (SQLSTATE 0A000) now retryable instead of permanent

v0.1.18

What's Changed

Added

• client.getInstanceStats(instanceId) — per-instance SystemStats (history event count, size, queue pending, KV usage)
• TypeScript declarations for getInstanceStats and SystemStats
• Admin API and e2e tests for orchestration stats

Changed

• Bumped duroxide to 0.1.27, duroxide-pg to 0.1.28
• Updated MAX_KV_KEYS to 150, MAX_KV_VALUE_BYTES to 65536

Fixed

• Removed local path overrides from Cargo.toml for CI compatibility