@warlock.js/seal 5.16.0 → 5.17.1

package/CHANGELOG.md

@@ -4,6 +4,13 @@ All notable changes to `@warlock.js/seal` are documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). `@warlock.js/*` packages are released in lockstep — every package shares the same version number, so a version below may list only the changes that affected this package.
 
+## 5.17.0 - 2026-09-21
+
+### Added
+
+- Granular `@warlock.js/seal/object` and `@warlock.js/seal/string` entry points with the `object` and `string` factories for schemas that do not need the complete `v` factory.
+- `redactValue` option on `v.validate(schema, data, options)`: when set, the `:value` placeholder renders that string instead of the submitted input, both in the attributes handed to `translateRule` and in author `errorMessage` templates. It does not cover a custom rule that concatenates raw input into its own message text. Unset keeps the current behaviour. Per-call options replace the global config, so pass `{ ...getSealConfig(), redactValue }` to keep your translators.
+
 ## 5.13.0 - 2026-09-17
 
 ### Fixed

package/README.md

@@ -18,6 +18,28 @@ yarn add @warlock.js/seal
 pnpm add @warlock.js/seal
 ```
 
+## Granular object and string entry points
+
+When a module only needs object and string schemas, import those factories from
+their dedicated entry points instead of the complete `v` factory:
+
+```typescript
+import { object } from "@warlock.js/seal/object";
+import { string } from "@warlock.js/seal/string";
+
+const commentSchema = object({
+  comment: string().trim().required().minLength(3),
+});
+
+const result = await commentSchema["~standard"].validate({
+  comment: "  Hello  ",
+});
+```
+
+`object` and `string` create the same schema classes with their chain methods
+and Standard Schema bridge. Use the package-root `v` factory when the schema
+also needs other factories.
+
 ## 🚀 Quick Start
 
 ```typescript