Skip to content

Releases: nhost/hasura-auth

v0.40.3-beta0

18 Jul 05:21
Compare
Choose a tag to compare
v0.40.3-beta0 Pre-release
Pre-release

Full Changelog: v0.40.2...v0.40.3-beta0

v0.40.2

10 Jul 19:39
736fc85
Compare
Choose a tag to compare

Changes

v0.40.1

01 Jul 13:36
2a65455
Compare
Choose a tag to compare

Changes

v0.40.0

01 Jul 10:38
c42e65b
Compare
Choose a tag to compare

Changes

NOTE: This finalizes the migration from node.js to go. Users should expect performance improvements and massive memory gains (up to 90-95% memory reduction).

v0.39.1

25 Jun 12:15
92b594c
Compare
Choose a tag to compare

Changes

v0.39.0

13 Jun 10:37
35fb119
Compare
Choose a tag to compare

Changes

v0.38.1

30 May 08:16
4d56ac9
Compare
Choose a tag to compare

Changes

v0.38.1-beta2

29 May 05:53
Compare
Choose a tag to compare
v0.38.1-beta2 Pre-release
Pre-release
fix: more fixes to webauthn schema that were causing problems

v0.38.0

28 Mar 07:40
7439685
Compare
Choose a tag to compare

Changes

Potential breaking change

⚠️⚠️⚠️ #617 changes the way refresh tokens work. Previously when you utilized the /token endpoint to refresh the token, the current refresh token was reused in the response. For instance:

POST /token {"refresh_token": "same-random-refresh-token"}
  {"access_token": "...", "refresh_token": "same-random-refresh-token"}

After the #617 the auth service invalidates the used token and returns a new one:

POST /token {"refresh_token": "random-refresh-token"}
  {"access_token": "...", "refresh_token": "some-other-random-refresh-token"}

If you are using our official SDKs this is a transparent change as our SDK already updated the refresh token from the response and you don't need to worry about this change. If you are not using our SDK we recommend you to make sure you are updating the refresh token based on the response prior to upgrading.

v0.37.1

19 Feb 08:07
f93014d
Compare
Choose a tag to compare

Changes