@ambushsoftworks/nestjs-payments-graphql 0.7.0-rc.3 → 0.7.0

package/CHANGELOG.md

@@ -28,7 +28,7 @@ prose for buried obligations. The marker was introduced in v0.4.0 and
 
 ## [Unreleased]
 
-## [0.7.0] - 2026-09-19
+## [0.7.0] - 2026-09-20
 
 > **Upgrade notes.** One optional database column, required only if you want
 > the feature.
@@ -169,6 +169,20 @@ nothing, so consumers heard auto-pauses and never manual ones; and
 `InvoiceNumberService` had a retry loop that ran once, a constant that meant
 nothing, and an unreachable exception below it.
 
+### Testing
+- **+54 specs, 605 across 25 suites.** New: `e-transfer.service.spec.ts`, which
+  the service had gone without entirely — the code a client transcribes into a
+  bank's message field by hand had no test that it excludes the characters its
+  own comment claimed it excluded, and it did not.
+- **Three test doubles were looser than the interfaces they stand for**, each
+  found only when something started depending on the real behaviour: the
+  auto-charge repository double had no `findById` though the interface requires
+  it, the payment-jobs email double resolved `undefined` where the real method
+  resolves a boolean, and `IPaymentRepository`'s double enforced the `Payment`
+  unique constraint but not its foreign key — which is why the unknown-invoice
+  webhook bug reached a consumer's production. A double that cannot fail for
+  the right reason is not a test.
+
 ### Changed
 - **`strict` is on.** The audit filed it as a release-sized job; it was one
   line. Every error came from `strictPropertyInitialization`, which GraphQL

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ambushsoftworks/nestjs-payments-graphql",
-  "version": "0.7.0-rc.3",
+  "version": "0.7.0",
   "description": "NestJS payments module with GraphQL support — invoicing, payment processing, recurring billing, and email notifications",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",