feat(objectql,spec)!: enforce a field's declared precision (total digits) at the write seam — max_precision (#19992)
#28873
Triggered via pull request
September 28, 2026 10:48
Status
Success
Total duration
1m 15s
Artifacts
–
pr-automation.yml
on: pull_request
Check PR Size
0s
Check Changeset
1m 11s
Auto Label
0s
Annotations
2 notices
|
Check Changeset:
.changeset/19992-field-precision-write-seam.md#L0
ADR-0087 exemption (no-migration-prescription): Nothing authorable moves: `precision` keeps its key, its type (`z.number().int().min(0)`) and its legality on every field type, and no stored metadata representation changes, so `objectstack migrate meta` has nothing to rewrite and the ledger has no row to gain. What narrows is the record validator's write accept set for values under an already-declared count, which is runtime behaviour, not an authored shape. The spec edits add a member to a closed enum, two message templates and a describe; none removes or renames anything an author can write. The other categories are closed on facts: both packages publish (not `unpublished`); no ADR-0087 id is minted here and none covers this (not `registered` / `already-registered`); and runtime behaviour changes, not only a TypeScript declaration (not `runtime-interface-only` / `type-surface-only`).
|
|
Check Changeset
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|