@ambushsoftworks/nestjs-auth-graphql 0.9.0-rc.5 → 0.9.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/CHANGELOG.md +10 -17
  2. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -27,7 +27,7 @@ for buried obligations. **The marker was introduced in 0.9.0 and has not been
27
27
  retro-applied**, so it is reliable from 0.9.0 onward only. Convention adopted
28
28
  from `@ambushsoftworks/nestjs-payments-graphql`.
29
29
 
30
- ## [0.9.0] - Unreleased
30
+ ## [0.9.0] - 2026-09-14
31
31
 
32
32
  Three independent workstreams land here: a trim of the email interface surface
33
33
  down to what the package actually fires, a fix making
@@ -40,22 +40,15 @@ seven `features` flags that nothing ever read are removed — see **Breaking**;
40
40
  and the package's logs stop carrying raw email addresses, IP addresses and
41
41
  phone numbers — see **Security**.
42
42
 
43
- > Published as a release candidate under the `next` dist-tag first, so the
44
- > verification and password-reset emails could be confirmed through a real
45
- > mail client before reaching `latest`. That last hop — a mail client
46
- > rendering the link — is exactly where the original defect lived and the one
47
- > thing no test suite in this repo can exercise. Install the candidate with
48
- > `npm install @ambushsoftworks/nestjs-auth-graphql@next`.
49
- >
50
- > **Test against `0.9.0-rc.5`.** `rc.3` added the move to bcrypt 6
51
- > (**Security**) and dropped eight stale compiled files `rc.2` had shipped by
52
- > mistake (**Fixed (release tooling)**); the copy of this note inside `rc.3`
53
- > claims nothing else changed, which is wrong on that point. `rc.4` removed
54
- > seven unread `features` flags (**Breaking**) and made the build start from an
55
- > empty `dist/`. `rc.5` keeps personal data out of the package's logs
56
- > (**Security**) and stops code mode warning about a base URL it does not need
57
- > (**Fixed**). `rc.1` predates the account-status fix in **Security** and still
58
- > has the suspension window open.
43
+ > Shipped through five release candidates on the `next` dist-tag before
44
+ > reaching `latest`; this release is the content of `0.9.0-rc.5` under its
45
+ > final version. Ariadne verified token and code mode end to end before
46
+ > `rc.1`, and Lift ran its automated staging checks and its real-inbox, phone
47
+ > and Google sign-in checks against `rc.3`. What arrived after that — the
48
+ > `features` flag removal and clean build in `rc.4`, and personal data in logs
49
+ > and the code-mode base URL in `rc.5` — was verified by this package's test
50
+ > suite and against the published candidates, not on an adopter's staging.
51
+ > `rc.2` carried eight stale compiled files; see **Fixed (release tooling)**.
59
52
 
60
53
  ### ⚠ External configuration required
61
54
  - **`verificationMode: 'token'` requires your frontend to serve two routes.**
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ambushsoftworks/nestjs-auth-graphql",
3
- "version": "0.9.0-rc.5",
3
+ "version": "0.9.0",
4
4
  "description": "Production-grade authentication package for NestJS with GraphQL, supporting JWT, OAuth, email/SMS verification, and biometric auth",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",