This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
hasura-auth@0.20.0
Minor Changes
50a1b1d: chore: migrate refresh_token column to id
⚠️ Warning: This is a breaking change.
We've renamed the refresh_token column to id. While this change will improve the functionality of Hasura Auth, it may cause issues for any permissions or relationships that were using the old refresh_token column.
Please note that any permissions or relationships that were using the refresh_token column will be affected by this change. If you're using the refresh_token column in any way, you'll need to update your code to use the new id column and ensure that your app works as expected.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
hasura-auth@0.20.0
Minor Changes
50a1b1d: chore: migrate
refresh_token
column toid
⚠️ Warning: This is a breaking change.
We've renamed the
refresh_token
column toid
. While this change will improve the functionality of Hasura Auth, it may cause issues for any permissions or relationships that were using the oldrefresh_token
column.Please note that any permissions or relationships that were using the
refresh_token
column will be affected by this change. If you're using therefresh_token
column in any way, you'll need to update your code to use the newid
column and ensure that your app works as expected.