v1.1.7

[JS] Update napi (#169)

v1.1.6

Bump versions for optimizations + Ruby `conditions?` (#168)

v1.1.5

Bump version: patch for optimizations (#160)

v1.1.4: [JS] Remove extra files from package (#138)

Make the package smaller.

Fix CI issues:
 https://github.com/rust-lang/rust/pull/131477
The PR doesn't directly mention undefined N-API symbols. But the fact
that the runner image updated Rust from 1.90 to 1.91,
and that's when the linking failures started, is compelling evidence.
The fix I added (the -undefined dynamic_lookup flags) is
the correct solution regardless - it's been the standard approach for
N-API addons on macOS for years.

  Why the linker flags are now needed:

1. GitHub Actions runner image update: The macos-15-arm64 runner image
was updated from version 20251021.0066 (used in Oct 26
  successful build) to 20251104.0104 (used in Nov 7 failed builds)
2. Rust version upgrade: The runner image update included Rust 1.90.0 →
1.91.0
3. Rust 1.91 macOS linking changes: Rust 1.91
https://github.com/rust-lang/rust/pull/131477 via the SDKROOT
environment
variable. This appears to have made the linker stricter about undefined
symbols in cdylibs.
4. The fix: Adding -undefined dynamic_lookup linker flags for macOS
targets is the standard solution for N-API native addons,
as these symbols are intentionally undefined and resolved at runtime by
Node.js. The flags tell the macOS linker to allow
  these undefined symbols.

v1.1.3

[imports] Optimize and correct cycle detection (#135)

v1.1.2

[configurable strings] Fix bug to support Configurable Strings in imp…

v1.1.1

[Configurable Strings] Do not require any properties (#129)

v1.1.0: Bump versions (#123)

configurable strings: Correct issues with getting string for all options and when there are overrides

v1.0.0

[Rust][JS] Bump versions (JS: 1.0.0) (#113)

v0.10.0

Track dependents + Bump versions (#103)