Skip to content

Releases: tediousjs/tedious

v15.1.1

01 Nov 14:49
cbe31af
Compare
Choose a tag to compare

15.1.1 (2022-11-01)

Bug Fixes

  • clear connection timeout on connection error (#1262) (cbe31af)

v15.1.0

17 Aug 20:34
ece396a
Compare
Choose a tag to compare

15.1.0 (2022-08-17)

Features

v15.0.1

26 Jul 08:11
5015634
Compare
Choose a tag to compare

15.0.1 (2022-07-26)

Bug Fixes

  • set maximum supported TLS version to 1.2 (#1471) (5015634)

v15.0.0

11 Jul 17:56
f225dbc
Compare
Choose a tag to compare

15.0.0 (2022-07-11)

chore

  • drop support for Node.js 12 (121f3a5)

Features

  • change default value for trustServerCertificate option to false (04ebc29)
  • remove domain option for azure-active-directory-password authentication (85a2b89)
  • remove default value for clientId option of azure-active-directory-password authentication (8885e1f)

BREAKING CHANGES

  • The domain option was replaced by the tenantId option.
  • Using the azure-active-directory-password
    authentication type now requires specifying the clientId option of an
    Azure Application. The application has to have public client flows
    enabled and has to have user_impersonation permissions for Azure SQL
    Database. The user account that is being used also has to be assigned
    to the application, and has to grant consent (either explicitly or via
    admin consent).
  • The default value for the trustServerCertificate option
    changed from true to false.
  • tedious no longer supports Node.js 12.x.

v15.0.0-beta.1

11 Jul 08:22
89ef3b2
Compare
Choose a tag to compare
v15.0.0-beta.1 Pre-release
Pre-release

15.0.0-beta.1 (2022-07-11)

Features

  • remove domain option for azure-active-directory-password authentication (a6dc9fa)
  • remove default value for clientId option of azure-active-directory-password authentication (438986e)

BREAKING CHANGES

  • The domain option was replaced by the tenantId option.
  • Using the azure-active-directory-password
    authentication type now requires specifying the clientId option of an
    Azure Application. The application has to have public client flows
    enabled and has to have user_impersonation permissions for Azure SQL
    Database. The user account that is being used also has to be assigned
    to the application, and has to grant consent (either explicitly or via
    admin consent).

v14.7.0

29 Jun 20:36
318aacc
Compare
Choose a tag to compare

14.7.0 (2022-06-29)

Features

  • support NTLM authentication on Node.js 17+ out of the box (#1451) (318aacc)

v14.6.1

18 Jun 09:19
7ebd236
Compare
Choose a tag to compare

14.6.1 (2022-06-18)

Bug Fixes

v14.6.0

08 Jun 19:19
57a50d4
Compare
Choose a tag to compare

14.6.0 (2022-06-08)

Features

  • fail ntlm auth gracefully when md4 hashing is not available (#1400) (57a50d4)

v14.5.0

27 Apr 20:15
6dea6c3
Compare
Choose a tag to compare

14.5.0 (2022-04-27)

Features

  • return aggregate errors (d8575b2)

v14.4.0

17 Mar 21:41
4261073
Compare
Choose a tag to compare

14.4.0 (2022-03-17)

Features

  • add azure-active-directory-default as an authentication option (13ee60f)