Skip to content

Releases: shahradelahi/node-vault

v1.0.0

08 Oct 13:54
c82fc12
Compare
Choose a tag to compare

Major Changes

  • 3775bf3: Fix: Using the environment's global fetch API instead of undici.

    This change makes this library more compatible with JavaScript runtimes that do not support Node.js modules. If you want to use undici again, use the Custom Fetcher feature.

  • f922ba9: BREAKING: The responses of commands are wrapped in a record with type of SafeReturn<T, VaultError>.

    This record contains two properties:

    • data: The data property for successful responses. The value depends on the command.
    • error: The error property for error responses. The type is VaultError, which is a subclass of Error.

    Read Migration guide for more details on how to use it.

  • e2f73e7: Fix: Switched license from GPL-3.0 to MIT, to make the project more open and permissive.

v1.0.0-canary.0

27 Jun 05:22
v1.0.0-canary.0
c9c1b4f
Compare
Choose a tag to compare
v1.0.0-canary.0 Pre-release
Pre-release
Release Notes:

- feat: atomic http responses by @shahradelahi in https://github.com/shahradelahi/node-vault/pull/39

**Full Changelog**: https://github.com/shahradelahi/node-vault/compare/v0.2.5...v1.0.0-canary.0

v0.2.5

30 May 15:14
bac661b
Compare
Choose a tag to compare

Patch Changes

  • 9f41e99: fix: the fetcher parameter was not being assigned to the client

v0.2.4

26 May 18:18
71e758f
Compare
Choose a tag to compare

Patch Changes

  • 2a24739: fix: type issues with default write command
  • 3bb7c15: fix: the bug where the args for aws.stsCredentials were not being sent

v0.2.3

25 May 21:49
865148a
Compare
Choose a tag to compare

Patch Changes

  • 90d185e: feat: Capability to generate AWS credentials for STS path