Support and versioning
How versions are numbered, what a release can change, which versions get fixes, what is required to run it, and what 1.0 will mean.
Versions
The package follows semantic versioning with the usual 0.x caveat: below 1.0, a minor version (0.4 to 0.5) can change behaviour, and a patch (0.5.0 to 0.5.1) only fixes bugs and updates documentation.
Every release is in the changelog. A change that alters behaviour by default is listed under Changed with how to opt out, and anything you have to do (a database change, a known error) is in Upgrading. Pin the minor while you test ("@umohpyro/better-auth-nuvion": "~0.5.0"), then widen the range.
What gets fixes
Bug and security fixes go into the latest minor version. Older minors are not backported before 1.0, so upgrading is the fix. Security reports are handled as described in Security.
Deprecations
A feature that is going away is marked deprecated in the changelog and in the types at least one minor version before it is removed, with what to use instead.
What it needs
| Supported | |
|---|---|
| Better Auth | 1.7.0 or later, with the organization plugin |
| Node | 20 or later (the example and its tests use 24) |
| React | 18 or later, only for the optional admin view |
| Databases | Anything Better Auth supports. Tested on SQLite, Postgres, MariaDB, and the Drizzle and Prisma adapters on Postgres; see Status and limits for what is not tested yet |
| Nuvion | The current Nuvion API. It runs against Nuvion's test environment by default; set baseUrl for production |
Getting help
For a bug or a question, open an issue on the repository with the plugin version, your Better Auth version, your database, and what you expected and saw. Please remove keys and personal data. This is an independent project, so replies are best effort. Anything about your Nuvion account, entities, KYC or the Nuvion API itself goes to Nuvion's support.
What 1.0 will mean
The public API (options, endpoints, hooks, client methods and the admin view's class names) stays compatible within 1.x, with changes added rather than altered. We will get there when production use has been verified, the databases listed as not tested run in CI, a security review is done, and the options and endpoints have stopped moving.