@bymax-one/nest-config 1.1.1 → 1.1.2

package/CHANGELOG.md

@@ -11,6 +11,38 @@ as the GitHub Release body, so each released version needs a matching
 
 ## [Unreleased]
 
+## [1.1.2] - 2026-08-14
+
+**Documentation only.** `dist/` is byte-identical to `1.1.1`, verified by hashing every file in
+the published tarball against a local build. Inside the package only `README.md`, `CHANGELOG.md`
+and the `version` field of `package.json` differ.
+
+### Documentation
+
+- **The `1.1.1` apply-note understated the work for a consumer with a mutation gate.** It said
+  a derived backend has nothing to change, which is true for correctness and wrong as an
+  estimate. Under Stryker, a message string literal is a mutant: authoring messages for rules
+  that had none converts operator-facing prose into tested behavior, and a repo gating at
+  `break: 100` fails until an assertion pins each message. Reported by a consumer adopting
+  `1.1.1`, which added one assertion per message to keep its gate green.
+
+  The honest version of the note: **upgrading changes nothing** — a rule that carries no
+  message renders exactly as it did before, verified byte-for-byte on a real boot. **Writing
+  the messages the release makes worth writing is real work**: wherever mutation testing is a
+  gate, every message needs an assertion that covers it — one assertion on the rendered report
+  can cover several — and that is the work the release exists to enable.
+
+  Also worth knowing before writing them: a rule whose variable is _absent_ rendered
+  `missing required value` on `1.1.0`, not `invalid value`. For a conditionally-required
+  variable that is the more misleading of the two — nothing was forgotten, another variable
+  made it required — so the before/after is larger than the `invalid value` case suggests.
+
+- The mutation badge read **99.59%**; the score measured as the `v1.1.1` release gate is
+  **99.61%**. The denominator grew with the new code — 14 more killed mutants in
+  `env-validator.ts`, the only file the release changed executably, and the same single
+  counted survivor — so the badge, the README claim and `docs/mutation_testing_results.md`
+  now state the measured number, with a dated re-run entry recording it.
+
 ## [1.1.1] - 2026-08-14
 
 ### Fixed
@@ -231,4 +263,5 @@ have regressed from. They are kept because the reasoning is worth having.
 [1.0.3]: https://github.com/bymaxone/nest-config/compare/v1.0.2...v1.0.3
 [1.1.0]: https://github.com/bymaxone/nest-config/compare/v1.0.3...v1.1.0
 [1.1.1]: https://github.com/bymaxone/nest-config/compare/v1.1.0...v1.1.1
-[Unreleased]: https://github.com/bymaxone/nest-config/compare/v1.1.1...HEAD
+[1.1.2]: https://github.com/bymaxone/nest-config/compare/v1.1.1...v1.1.2
+[Unreleased]: https://github.com/bymaxone/nest-config/compare/v1.1.2...HEAD

package/README.md

@@ -14,7 +14,7 @@
   <a href="https://www.npmjs.com/package/@bymax-one/nest-config"><img src="https://img.shields.io/npm/dm/@bymax-one/nest-config?style=flat-square&colorA=000000&colorB=000000" alt="npm downloads" /></a>
   <a href="https://github.com/bymaxone/nest-config/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/bymaxone/nest-config/ci.yml?branch=main&style=flat-square&colorA=000000&label=CI" alt="CI status" /></a>
   <a href="https://github.com/bymaxone/nest-config/actions/workflows/ci.yml"><img src="https://img.shields.io/badge/coverage-100%25-brightgreen?style=flat-square&colorA=000000" alt="coverage" /></a>
-  <a href="https://github.com/bymaxone/nest-config/blob/main/docs/mutation_testing_results.md"><img src="https://img.shields.io/badge/mutation-99.59%25-brightgreen?style=flat-square&colorA=000000" alt="mutation score" /></a>
+  <a href="https://github.com/bymaxone/nest-config/blob/main/docs/mutation_testing_results.md"><img src="https://img.shields.io/badge/mutation-99.61%25-brightgreen?style=flat-square&colorA=000000" alt="mutation score" /></a>
   <a href="https://scorecard.dev/viewer/?uri=github.com/bymaxone/nest-config"><img src="https://api.scorecard.dev/projects/github.com/bymaxone/nest-config/badge?style=flat-square" alt="OpenSSF Scorecard" /></a>
   <a href="https://github.com/bymaxone/nest-config/blob/main/LICENSE"><img src="https://img.shields.io/github/license/bymaxone/nest-config?style=flat-square&colorA=000000&colorB=000000" alt="license" /></a>
   <a href="https://www.typescriptlang.org/"><img src="https://img.shields.io/badge/TypeScript-strict-3178C6?style=flat-square&logo=typescript&logoColor=white" alt="TypeScript" /></a>
@@ -514,7 +514,7 @@ Configuration decides whether a process may start at all, so the suite is held t
 beyond "the tests pass".
 
 - ✅ **100% line coverage** — statements, branches, functions and lines, enforced as a gate
-- ✅ **99.59% mutation score** — verified with [Stryker](https://stryker-mutator.io/) at
+- ✅ **99.61% mutation score** — verified with [Stryker](https://stryker-mutator.io/) at
   `break: 95`; ten provable equivalents carry their reason inline, and the one survivor left
   is an equivalent no directive can reach, so it stays counted rather than silenced
   ([report](./docs/mutation_testing_results.md))

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bymax-one/nest-config",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "description": "Typed and validated environment configuration entry point for NestJS 11 applications, built on Zod v4.",
   "author": "Bymax One <support@bymax.one>",
   "license": "MIT",