NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
pub.dev, #5410 most downloaded on pub.dev
Generates immutable models from Ack schemas and validated schemas from Dart classes
Latest stable
1.7.1
Last release 16 days ago
06 Nov 2026
Release timing varies
gaps range from 8 days to 3 months
Nearly every release is documented
notes for 12 of 12 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
35 releases · first in 2025
Drag across the ruler to compare, or tap a release to open it.
Breaking: Is…/Has… rule annotations replace the Validate namespace. Validate remains as deprecated redirects and is removed before Ack 2.0.0.
>=3.13.0 and Flutter >=3.47.0.Is…/Has… rule annotations replace the Validate namespace.
Validate remains as deprecated redirects and is removed before Ack 2.0.0.ack and ack_generator at 2.0.0-beta.3.
Upgrade the five packages together.>=3.13.0 (Flutter >=3.47.0, which bundles
Dart 3.13.0). Dart 3.13 adds the primary constructors that the class-first
examples use. Apps on Flutter 3.41 to 3.46 cannot use Ack 2.0.ack: ^2.0.0-beta.3. Generation reads the AckRule types.Is…/Has… annotation type.
Deprecated Validate constructors evaluate to the same annotations and
generate identical code. Validate.ipv4() and Validate.ipv6() now
generate .ip(version: 4) and .ip(version: 6), the same constraints that
.ipv4() and .ipv6() build. Validate is removed before Ack 2.0.0.@HasMinLength, in diagnostics.fromJson field or method that is not a
Model Function(Map<String, dynamic>), such as a .parse tear-off or
another model's fromJson.static final schema = <Name>Schema.schema; in class-first examples
instead of the private codec variable. Both forms generate the same code.Your coding agent can read these notes before it upgrades. Set up the MCP server →
Breaking: Object defaults fill omitted keys; explicit JSON null requires a nullable property. Missing or null defaulted fields encode as the default.
@Validate.*, regenerate model parts, and upgrade all five packages together.toString() output.T? fields accept null unless
marked @Validate.notNull(); omitted keys still use their defaults.@Validate.*, including @Validate.required(), as the public annotation
API. No new annotations are required.ack: ^2.0.0-beta.2 for the matching default/null contract.Apply generated field presence and nullability rules to custom schemas, even when their wrappers already supply defaults or optional/nullable flags. Export only defaults supplied by the field's own default policy.
Emit one internal Ack field-policy helper instead of inline generic codecs.
Interpolate field values in generated schema-first toString() output
instead of printing the field references as literal text.
Use runtime-validated value models for custom dialects so inactive vocabulary keywords retain annotation semantics instead of adding generated constraints.
Use runtime-validated value models when supplied documents provide the
source schema's own dialect, so the supplied vocabularies decide validation.
Honor supplied dialect resources under alias URIs even when their JSON maps use dynamic or object key types, including bundled resources.
Normalize and copy string-keyed JSON maps before preserve-mode widening so external and bundled resources retain unknown properties for parse and encode regardless of their declared map key types.
Preserve exact integer bounds on generated number schemas beyond 2^53.
Infer JSON numbers in Ack.preserveBoundary(Ack.map(...)) field values, including duration milliseconds, as num. A wire value keeps each number as deco
Ack.preserveBoundary(Ack.map(...)) field values,
including duration milliseconds, as num. A wire value keeps each number as
decoded, and numeric schemas accept both 1 and 1.0.ack: ^2.0.0-beta.1 so consumers receive the corrected runtime
nullability, discriminated validation, and imported JSON Schema contracts.Ack.preserveBoundary(Ack.map(...)) fields, including dates, datetimes,
URIs, enums, explicit codec inputs and statically resolvable nonrecursive
lazy schemas.Object or Object? in
schema-first model constructors and copyWith. Reuse Ack's shared deep
copier; constructors still do not validate data. Opaque codec runtime values
retain their identity and container types.required as generated
field, discriminator, and capture-member names without changing their JSON
keys. Reserved words such as class remain rejected. Member validation now
follows the analyzer's keyword classification rather than a fixed word list.
dynamic remains rejected because it shadows the type in generated JSON
methods, not because it is a reserved Dart word.copyWith no-op null
arguments are parenthesized.Ack.anyOf(...) fields whose branches are all native JSON as JSON
Object values, including list items and map values, without an
Ack.preserveBoundary(...) wrapper. A branch may itself be an explicit
Ack.preserveBoundary(...) wire view.Ack.anyOf(...) field with a codec, Ack.instance<T>(), model
schema, or nullable branch, naming the field and the offending branch.
Ack.any() and Ack.anyOf(...) model roots remain unsupported, including
through type-erased aliases. Branches are proven from their static schema
types and statically resolvable initializers. A custom method whose declared
runtime type is Object or a JSON collection but that returns a codec cannot
be detected.First prerelease of Ack 2.0, published for ack, ack_generator, ack_json_schema_builder, ack_firebase_ai and ack_mcp_dart. It runs on stable Dart (3.13
First prerelease of Ack 2.0, published for ack, ack_generator, ack_json_schema_builder, ack_firebase_ai and ack_mcp_dart. It runs on stable Dart (3.13 language features, including primary constructors on @Schemable classes).
Breaking
@AckType, @AckInfer, @AckModel, @AckField and friends). Use @Schemable() on top-level schemas and on hand-written classes and unions.@Optional, @Min, @Matches, @Email, …) and package:ack/format_annotations.dart with the @Validate.* namespace.Ack.enumCodec (use Ack.enumValues) and the unused StandardSchemaV1; seal SchemaError and AckSchema.Ack.fromJsonSchema() defaults to assertFormats: false, matching Draft 2020-12; toJsonSchema() preserves imported Draft 2020-12 resources (use toJsonSchemaDraft7() for Draft-07 lowering).Added
@Validate.* presence and constraint annotations, exported from package:ack/ack.dart and package:ack/annotations.dart.JsonMaybe<T> for PATCH-style tri-state presence.@Schemable(schemas: [...]) and @AckKey('...') for custom schema registration and wire-name overrides..trim(), .toLowerCase(), .toUpperCase()) on StringSchema.Ack.fromJsonSchema()..g.dart part per library and applies scalar @Validate.* constraints to List/Set items.Full notes are in each package's CHANGELOG.md under 2.0.0-alpha.1.
ack: ^2.0.0-alpha.1..g.dart builder (#189): ack_generator:ack_generator is
now a SharedPartBuilder that emits <file>.g.dart directly with generated
toJson() / fromJson() helpers. The two-part .ack.dart and .ack.g.dart
builders and runtime json_serializable delegation are removed. Replace
part '<file>.ack.dart'; and part '<file>.ack.g.dart'; with a single
part '<file>.g.dart';.@AckType, @AckInfer, @AckModel, @AckField, *Type
extension-type model generation, top-level @Optional / @Required /
@NotNull / constraint classes, and the legacy @JsonKey(name: ...) fallback
in favor of @Schemable(), @Validate.*, and @AckKey('...') (#188, #189, #191).@Validate.* presence and constraint annotations (@Validate.optional(),
@Validate.required(), @Validate.notNull(), @Validate.notEmpty() on
String/List/Set, etc.) from package:ack/ack.dart across field
declarations and primary/generative constructor parameters, as well as
static final schema = _<name>Schema; on class-first models (#191).JsonMaybe<T> fields in @Schemable() class-first models for PATCH
tri-state presence (#148).@AckKey('...') directly without package:json_annotation (#189).@Schemable() class fields via:
@Schemable(schemas: [...]) on the class, enclosing sealed union, current
library; directive, or an imported library; directiveT.schema / T.schema<...>()AckSchema<Boundary, T>
variable, getter, or zero-argument function in the current library (#185).StringSchema normalizers (.trim(), .toLowerCase(),
.toUpperCase()) in schema-first @Schemable() models.ack_generator:ack_json_schema builder and generateAckSchemaLibrary()
API: ack_generator:ack_json_schema emits <name>.schema.dart from
lib/**/*.schema.json Draft 2020-12 documents, which
ack_generator:ack_generator compiles into <name>.schema.g.dart typed
models or validated value-model libraries (#167).@Validate.* constraints on List and Set fields and
parameters to the items, alongside the collection's own constraints:
@Validate.min(1) @Validate.minItems(1) List<int> infers
Ack.list(Ack.integer().min(1)).minItems(1).Object fields through a class-level or union-level
@Schemable(schemas: [...]) entry whose schema targets Object; Object?
fields still infer Ack.any().Keep the generator's JSON dependencies compatible with the supported Dart 3.9 SDK, including clean builds in consumer packages: ack_generator bounds s
ack_generator bounds source_helper below 1.4 so json_serializable 6.14 compiles on Dart 3.9 through 3.11. Newer SDKs can still select json_serializable 6.15 (#248).Add @Schemable() as the unified annotation for schema-first and class-first generation; deprecate @AckInfer() and @AckModel() for removal in 2.0.0.
ack_annotations; annotations now ship in ack (package:ack/ack.dart, package:ack/annotations.dart, and package:ack/format_annotations.dart).@Schemable() as the unified annotation for schema-first and class-first generation; deprecate @AckInfer() and @AckModel() for removal in 2.0.0.@Pattern to @Matches (keeping a deprecated Pattern alias in package:ack/annotations.dart) and remove the json_annotation re-export from ack.schema (including extension types, enums, and generic schema<A>() factories), and generate a static final schema shorthand on schema-first models.$ClassCopyWith<Class> getter for copyWith on generated models, support explicit description options and @description doc tags (#175), require unique boundary items on constrained Set fields, and escape control characters in generated string literals (#164).Ack.fromJsonSchema() with multipleOf (exact decimal division), contains, if/then/else, built-in string and numeric format assertions, x-* vendor extensions, Draft-07 $schema URIs, and JsonSchemaValidationError location diagnostics (keyword, keywordLocation, documentUri, pointer).pattern expressions now compile in ECMA-262 Unicode mode (u); native Ack.string().matches() is unchanged.safeParse, safeEncode, toJsonSchema(), imported JSON Schema validation, and collection parse/encode results.ack_generator requires ack: ^1.7.0; adapter dependency minimums are unchanged).ack: ^1.7.0 and read annotations from package:ack (ack_annotations
is removed). Regenerate models after upgrading (@Schemable.generatedJson
replaces @AckInfer.jsonSerializable).JsonConverter annotations on class-first models and fields so
json_serializable cannot bypass Ack's runtime validation bridge.copyWith to a getter returning a typed
$ClassCopyWith<Class> interface, turning mistyped arguments into
compile-time errors while preserving model.copyWith(field: value) call sites
and explicit null clearing.@Schemable() for both schema-first and class-first generation, and
emit a static final schema shorthand on schema-first models.schema getter or generic
schema<A>() factory (including extension types, enums, and per-type-argument
schema parameters).description options on @Schemable and @AckField,
single-line @description doc tags, and string format annotations.package:ack_generator/inference.dart.uniqueItems: true) on class-first Set
fields with @MinItems, @MaxItems, or @UniqueItems.// ignore_for_file: type=lint and // coverage:ignore-file headers and
member doc comments in generated .ack.dart and .ack.g.dart parts.@Schemable options target the wrong declaration kind, or when
@AckField(schema:) is generic or returns an incompatible schema type.Set<Set<T>> to the outer set and escape
control characters in all generated string literals (#164).No new breaking changes or generator migrations are introduced in 1.7.0-beta.7 . When upgrading from 1.6.2 or earlier 1.7.0 betas:
All five packages are aligned at 1.7.0-beta.7: ack, ack_generator, ack_json_schema_builder, ack_mcp_dart, and ack_firebase_ai.
multipleOf in imported JSON Schemas (#214): Ack.fromJsonSchema() now validates multipleOf for number and integer schemas using exact decimal division (shared with native .multipleOf()) and reports keywordLocation on failures.format assertions and x-* extensions in imported JSON Schemas (#216): Ack.fromJsonSchema() now validates built-in string formats (date, email, uuid, uri, ipv4, and ipv6, in addition to date-time), standard numeric formats (int32, int64, uint32, uint64, float, and double), and accepts x-* vendor extension annotations (such as x-transformed).$schema URI support (#217): Ack.fromJsonSchema() now accepts http(s)://json-schema.org/draft-07/schema (with or without a trailing #), allowing schemas exported by .toJsonSchema() to be re-imported directly.Ack.fromJsonSchema() reads typed node fields directly instead of per-node keyword maps, toJsonSchema() skips redundant subtree walks when constraints do not project nested keywords, and Ack.object(), Ack.list(), and Ack.map() return detached unmodifiable views without a second collection copy.No new breaking changes or generator migrations are introduced in 1.7.0-beta.7. When upgrading from 1.6.2 or earlier 1.7.0 betas:
1.7.0-beta.4 or earlier: Imported pattern expressions compile in ECMA-262 Unicode mode (u flag); see the 1.7.0-beta.5 release notes.1.7.0-beta.2 or earlier: Annotations ship in package:ack with @Schemable() as the unified entry point; see the 1.7.0-beta.3 changelog.No new breaking changes or generator migrations are introduced in 1.7.0-beta.6 . When upgrading from 1.6.2 or earlier 1.7.0 betas:
All five packages are aligned at 1.7.0-beta.6: ack, ack_generator, ack_json_schema_builder, ack_mcp_dart, and ack_firebase_ai.
JsonSchemaValidationError now includes keywordLocation (and serializes it in toMap()), reporting the evaluation path from the root schema to the failing keyword across each $ref traversal.uniqueItems error path (#207): Imported uniqueItems validation failures now report the array path (for example #) instead of the duplicate element index, matching native Ack.list(...).unique().safeParse and safeEncode cache default root context names per schema type, and Ack.fromJsonSchema() reuses compiled pattern regular expressions and validates copied JSON inputs in fewer passes. Error output is unchanged.No new breaking changes or generator migrations are introduced in 1.7.0-beta.6. When upgrading from 1.6.2 or earlier 1.7.0 betas:
1.7.0-beta.4 or earlier: Imported pattern expressions compile in ECMA-262 Unicode mode (u flag); see the 1.7.0-beta.5 release notes.1.7.0-beta.2 or earlier: Annotations ship in package:ack with @Schemable() as the unified entry point; see the 1.7.0-beta.3 changelog.Imported `pattern` expressions now use ECMA-262 Unicode mode. This is a deliberately accepted breaking change in 1.7.0, affecting users upgrading from…
contains and if/then/else.keyword, documentUri, and pointer through JsonSchemaValidationError. Source pointers correctly encode URI fragments containing percent signs, spaces, #, and Unicode.Imported pattern expressions now use ECMA-262 Unicode mode. This is a deliberately accepted breaking change in 1.7.0, affecting users upgrading from stable 1.6.2 or earlier 1.7.0 betas.
. matches one code point: ^.$ accepts 😀, while ^..$ no longer matches its two UTF-16 code units. Review identity escapes too; replace ^\d{3}\-\d{4}$ with ^\d{3}-\d{4}$ outside character classes. Invalid Unicode-mode patterns fail import with an invalid_schema diagnostic.
Native Ack.string().matches() retains its Dart regex behavior. A native pattern can behave differently or fail import after export to JSON Schema.
Existing SchemaValidationError catches still work. Consumers requiring an exact runtime type or serialized error-map shape should allow the new subtype and its three additional fields. Initial null-input and JSON-value checks retain their existing Ack error types.
The beta.3 annotation and generator migrations still apply to users upgrading from older versions.
Full workspace tests, minimum Dart/Flutter checks, API comparison against 1.6.2, deterministic generation, Draft-7 validation, documentation validation, and zero-warning publish dry runs passed. The local aggregate passed 2,161 tests, including 394 generator tests; four opt-in Firebase live tests were skipped without credentials.
All five packages are aligned at 1.7.0-beta.4: ack, ack_generator, ack_json_schema_builder, ack_mcp_dart, and ack_firebase_ai.
All five packages are aligned at 1.7.0-beta.4: ack, ack_generator, ack_json_schema_builder, ack_mcp_dart, and ack_firebase_ai.
Ack.fromJsonSchema() now validates the supported date-time format automatically. Unsupported format labels continue to produce diagnostics.Ack.string().datetime() now accepts lowercase t and z on announced leap seconds.ack 1.7.0-beta.4 or later, without a new API or dependency minimum.final timestamp = Ack.fromJsonSchema({
'type': 'string',
'format': 'date-time',
});
timestamp.parse('2024-02-29T12:34:56.123456789+02:00');
Ack's strict JSON Schema importer supports a documented subset; this release does not claim full JSON Schema Draft 2020-12 support.
No new generator or annotation migration is introduced in beta.4. When upgrading from beta.2 or earlier, the beta.3 breaking migrations still apply: annotations moved into ack, @Schemable() is the unified entry point, and JsonKey is no longer re-exported. See the repository changelog for the full migration details.
The reviewed release commit passed CI, browser tests, release preflight, schema validation, API compatibility checks, and zero-warning publish dry runs for all five packages.
Release commit: 0023d152288fb69b2967d230481fe8b681606d8b.
ack dependency remains
at the first beta that supplies the required annotations.Files that use constraint annotations or the deprecated spellings also import package:ack/annotations.dart, with a prefix (as ack) where a name clashe…
ack_annotations package; the annotations ship in ack. Models
import package:ack/ack.dart (@Schemable, @AckField, @Optional,
@Required, @NotNull). Files that use constraint annotations or the
deprecated spellings also import package:ack/annotations.dart, with a
prefix (as ack) where a name clashes with another type. Format
annotations move to package:ack/format_annotations.dart.@Schemable() is the single annotation for schema-first and class-first
generation. @AckInfer() and @AckModel() are deprecated and will be
removed in 2.0.0.@Pattern to @Matches. The deprecated Pattern alias stays in
package:ack/annotations.dart; an unprefixed import of that library hides
dart:core's Pattern.ack no longer depends on json_annotation or re-exports JsonKey. A field
renamed with @JsonKey(name: ...) imports JsonKey from
package:json_annotation and the app depends on json_annotation.
AckModel.jsonSerializable and AckGeneratedJson.config are removed.schema resolves to it with
no annotation, including extension types, enums, and generic types through a
static schema<A>() method that can receive each type argument's schema.@AckField(schema:) functions, non-finite constraint values, @Schemable
options for the other target, and JsonConverter annotations on class-first
models.ack 1.7.0-beta.3.ack 1.7.0-beta.3, which owns the annotations.package:ack; the ack_annotations package is
removed. Import package:ack/ack.dart in annotated libraries, and
package:ack/annotations.dart where they use constraint annotations.@Schemable.generatedJson instead of
@AckInfer.jsonSerializable. Regenerate after upgrading.json_serializable configuration itself, from
caseStyle; ack carries no json_annotation types. @JsonKey(name: ...)
keeps working with JsonKey imported from package:json_annotation.JsonConverter annotation on a class-first model or field is rejected,
because json_serializable would apply it in place of Ack's validated
runtime bridge.@Schemable() drives both schema-first and class-first generation. The
deprecated @AckInfer() and @AckModel() spellings generate identical
output, and diagnostics name the annotation that was written.schema resolves to it with no
annotation, also per List / Set item and as a Map value. Extension
types are supported, and a generic type declares a static
schema<A>() method that is called with the field's type arguments
(Command.schema<CompletionAction>()). Schema-first objects may reference
the same members; void type arguments are supported only in class-first
fields. A @Schemable class may expose its facade as
static final schema = XSchema.schema;. The schema must produce the field's
type.schema<A>() that declares one positional AckSchema<Object, A>
parameter per type parameter A receives the schema inferred for each type
argument (Box.schema<Row>(RowSchema.schema)). Type arguments may be void
(Command.schema<void>()). An enum's static schema takes precedence over
Ack.enumValues.@Schemable options set for the other target (name on a class, class
options on a top-level schema) are rejected instead of ignored.@AckField(schema:) functions must produce the field's type; generic
functions, whose type arguments the generated call would drop, are rejected.Set<Set<T>> field apply to the outer set.Map
value.copyWith on @AckInfer() and @AckModel() models is a getter that returns a typed $ClassCopyWith interface. A wrongly typed argument is now a compile-ti
copyWith on @AckInfer() and @AckModel() models is a getter that returns
a typed $ClassCopyWith<Class> interface. A wrongly typed argument is now a
compile-time error instead of a runtime TypeError. Omission still keeps the
current value, and explicit null still clears a nullable field. Calls such
as model.copyWith(name: 'x') are unchanged. Code that tears off copyWith
as a function or mocks a model's copyWith method must be updated to use the
getter. Arguments statically typed Object or an incompatible type must be
narrowed or cast; dynamic arguments still compile.copyWith interface
compatible with the parent model's interface.Set field with @MinItems, @MaxItems, or @UniqueItems
now requires unique items at the JSON boundary, so the list's item count
matches the decoded set. Input with duplicate items, such as ['a', 'a'],
now fails validation instead of collapsing into a smaller set, and the JSON
Schema declares uniqueItems: true..ack.dart and .ack.g.dart parts start with
// ignore_for_file: type=lint and // coverage:ignore-file, so consumer
lint rules and coverage reports cover only hand-written source.$ack, and class-first
facades now have doc comments.ack and ack_annotations ^1.7.0-beta.2.description: or an @description doc
tag. This replaces the unreleased development behavior that exported every
field doc comment. Untagged prose and // comments never become schema
data. Shared AckSchemaInference.applyDescription uses the same rule.@AckInfer() models declare static final schema as a shorthand for
$ack.modelSchema. The generator omits this member when schema conflicts
with a field, discriminator, annotated declaration, or import prefix.@AckModel and @AckField
descriptions, plus single-line @description doc tags. Explicit annotation
values take precedence. Class descriptions apply to the wire object and
model codec; field descriptions apply only to that property.inference.dart exports shared type and constraint inference for other
generators. The class-first generator uses this library.@Pattern, discriminator, and key values containing a
newline or carriage return now produce valid Dart source.This coordinated release publishes ack, ack_annotations, ack_generator, ack_json_schema_builder, ack_mcp_dart, and ack_firebase_ai at version 1.6.2.
This coordinated release publishes ack, ack_annotations, ack_generator, ack_json_schema_builder, ack_mcp_dart, and ack_firebase_ai at version 1.6.2.
Ack.fromJsonSchema() now compiles the standard pattern keyword, restoring import of schemas exported from Ack. It uses an unanchored ECMA-262 search on strings and rejects invalid regular expressions at import time.Ack.fromJsonSchema() now accepts the standard propertyNames keyword to validate each object key against its subschema. Both keywords round-trip through Draft-7 export unchanged.The other five packages are version aligned and have no source or public API changes from 1.6.1. Compatible sibling dependency minimums remain unchanged.
See the publishing guide and changelogs for details.
Honor effective nullability consistently across unions, defaults, boundaries, codecs, object properties, and list-item validation.
All six ACK packages are aligned at 1.6.1. See the core package changelog for compatibility details and migration guidance.
Align with the coordinated Ack 1.6 release; this package has no runtime or public API changes from 1.5.0.
Infer open JSON class-first fields from their Dart types: Object → Ack.any(), Object? → Ack.any().nullable() (with the same presence annotations as St
Object →
Ack.any(), Object? → Ack.any().nullable() (with the same presence
annotations as String?), List<Object> → Ack.list(Ack.any()), and
Map<String, T> → Ack.map(<schema for T>), including
Map<String, Object?>. Map fields no longer require @AckField, which
still overrides an inferred schema. dynamic, List<Object?>, and
non-String map keys stay rejected; the dynamic error now suggests
Object?.Ack.any() and Ack.map(...) schema-first fields, inferring
Object/Object? and Map<String, T>. Ack.any() and Ack.map() model
roots stay rejected, including when reached through a variable.ack: ^1.5.0, because generated code now uses Ack.map.as Object? cast in generated copyWith bodies for
Object? fields.Ack.map values when the value schema is a variable declared
with .nullable(), such as Ack.map(nullableLabel).--fatal-infos: fieldless class-first
models no longer declare an unused self local, and nullable collection
bridges use null-aware access.Set<T>? fields; the set
codec now uses the non-null set type and presence adds nullability.@AckField(presence: ...) remains during migration and is deprecated for removal in 2.0.0.
Ack 1.4 adds @Optional(), @Required(), and @NotNull() so class-first
models can override JSON key presence independently of whether a present
value may be null. @AckField(presence: ...) remains during migration
and is deprecated for removal in 2.0.0.
null on a nullable Dart field with @NotNull().copyWith from the constructor type so optional non-nullable
codec fields compile and do not receive null.All six packages use version 1.4.0: ack, ack_annotations, ack_generator,
ack_firebase_ai, ack_json_schema_builder, and ack_mcp_dart.
The runtime, Firebase, JSON Schema, and MCP packages have no runtime or
public API changes from 1.3.0.
@Optional(), @Required(), and @NotNull() class-first field
annotations. Key presence stays separate from JSON null acceptance.copyWith nullability from the constructor parameter type
so optional non-nullable codec fields compile and do not receive null.@AckField(presence: ...) during migration with a deprecation warning;
reject conflicts with @Optional() / @Required().Ack 1.3 adds ack_mcp_dart, a small adapter that uses one ACK input contract for MCP tool discovery and runtime argument parsing with mcp_dart ^2.4.2.
Ack 1.3 adds ack_mcp_dart, a small adapter that uses one ACK input contract for
MCP tool discovery and runtime argument parsing with mcp_dart ^2.4.2.
All six packages use version 1.3.0: ack, ack_annotations, ack_generator,
ack_firebase_ai, ack_json_schema_builder, and ack_mcp_dart.
The existing five packages have no runtime or public API changes from 1.2.0,
and compatible dependency minimums remain at ^1.2.0.
Release tooling now uses Melos fixed versions and a shared workspace tag, compares APIs with 1.2.0, and supports resuming a partially completed publication.
ack_mcp_dart;
this package has no runtime or public API changes from 1.2.0.docs: align contracts and Firebase fixture dependencies by @leoafarias in https://github.com/conceptadev/ack/pull/126
Full Changelog: https://github.com/conceptadev/ack/compare/v1.1.0...v1.2.0
Full Changelog: v1.1.0...v1.2.0
@AckInfer() schema-first immutable models with parse/JSON/copy/value
APIs, named recursion, unions, codecs, defaults, nullability, additional
properties, immutable collections, and cross-library composition.@AckModel() class-first generation with private backing codecs, public
schema facades, constructor and field inference, unknown-property policies,
sealed unions, generated mixins, and inferred static fromJson aliases..ack.dart and .ack.g.dart builders so modern Ack output
remains separate from legacy and ordinary .g.dart generators.@AckType() generator path for removal in Ack 2.0.0. Use
@AckInfer() for schema-first models or @AckModel() for class-first
models. Existing Ack 1.1 output remains frozen and supported through 1.x.@AckType() analyzer, emitter, tests, and
ack_generator LibraryBuilder. Legacy *Type, Map, .args,
parse, safeParse, naming, getter, union, transform, and additional
property behavior is frozen until Ack 2.Error objects through runtime validation.wireSchema results in their original boundary
representation when nested models, collections, enums, or codecs decode.copyWith arguments from explicit null, so nullable
fields can be cleared in both schema-first and class-first models.copyWith arguments so a
consumer's const Object() cannot be mistaken for omission.AckUnknownPropertyPolicy / unknownProperties / captureField
contracts and delegate captured-map snapshots to
deepUnmodifiableJsonMap instead of emitting duplicate recursive helpers.JsonKey options and parameter placement, cross-library
class-first cycles, direct one-way transforms beneath codecs, and legacy
object fields whose schema expressions cannot be analyzed.@AckField codecs.>=10.0.0 <11.0.0.@AckType() to @AckInfer(),
add .ack.dart and .ack.g.dart, replace *Type/Map access with the
immutable class API, then use fromJson/toJson at the JSON boundary.@AckType() and .g.dart unchanged when migration is not desired.Ack 1.1.0 is a correctness-focused release that aligns runtime validation, generated schemas, and tooling with their documented contracts. It does not
Ack 1.1.0 is a correctness-focused release that aligns runtime validation, generated schemas, and tooling with their documented contracts. It does not change the public Dart API surface.
safeParse non-throwing for recoverable callback exceptions while
preserving Dart Error values so programming defects remain visible.t and z separators.multipleOf, IPv6, RFC 3339 date-times, range bounds, collection
limits, unions, and enum definitions consistently with JSON Schema.allOf, and export exact
list/object sizes with the correct Draft-7 keywords.source_gen diagnostics without undeclared debug-file output.Although the public API is unchanged, invalid or ambiguous inputs that were previously accepted may now fail earlier:
ArgumentErrors.Ack.list(item).nullable()), not its item.multipleOf.toJsonSchema().AckException from parse() when a recoverable constraint or
refinement callback throws; inspect the underlying cause for diagnostics.See the package changelogs for the complete behavior notes.
Ack.list(x.nullable()) build now fails; put nullability on the list with
Ack.list(x).nullable().)This patch hardens recursive schemas built with Ack.lazy against unbounded recursion.
This patch hardens recursive schemas built with Ack.lazy against unbounded recursion.
Ack.lazy / LazySchema (#122): recursive schemas now
enforce a maximum recursion depth (default 100) on parse, runtime validation, and
encode. Previously, cyclic or arbitrarily deep input could recurse without bound and
risk a stack overflow. Exceeding the limit now fails fast with a descriptive validation
error (lazy_max_depth: "Maximum recursion depth (N) exceeded.") instead of crashing.Ack.lazy(...) accepts an optional maxDepth (default LazySchema.defaultMaxDepth
= 100; must be >= 1), carried through copyWith, equality, and serialization.maxDepth check can't be expressed via
$ref and is omitted from the exported schema.Behavior note: recursion is now capped at depth 100 by default. Structures that legitimately nest deeper must pass an explicit higher
maxDepth.
The other packages (ack_annotations, ack_generator, ack_json_schema_builder,
ack_firebase_ai) are version-aligned to 1.0.1 with no functional changes.
Ack 1.0.0 is the first stable release of Ack, a schema validation library for Dart and Flutter. Ack helps you validate untrusted data at application b
Ack 1.0.0 is the first stable release of Ack, a schema validation library for Dart and Flutter. Ack helps you validate untrusted data at application boundaries, reuse the same schemas across runtime validation and JSON workflows, and generate typed wrappers when you want stronger ergonomics than map access.
Start with the documentation site or jump straight into the Quickstart Tutorial.
safeParse, SchemaResult, structured paths, and readable validation messages.@AckType() for extension types, typed getters, parse, and safeParse.toJsonSchema() and the reusable schema-model boundary for adapter authors.ack: core runtime validation library.ack_annotations: @AckType() annotation package.ack_generator: build_runner generator for typed schema wrappers.ack_json_schema_builder: adapter for json_schema_builder.ack_firebase_ai: Firebase AI structured-output schema adapter.Ack also publishes an llms.txt index with a compact overview of the packages, core APIs, code generation workflow, and common examples.
This release was validated with the full package test suites, documentation checks, example tests, and pub.dev dry-runs before publishing. All five packages are now available on pub.dev at version 1.0.0.
DoubleSchema and NumberSchema now reject non-finite values (NaN, Infinity, -Infinity) during runtime validation by default, aligning numeric schemas w
ackBreaking
DoubleSchema and NumberSchema now reject non-finite values (NaN, Infinity, -Infinity) during runtime validation by default, aligning numeric schemas with JSON-safe values.AckSchemaModel variants and a canonical AckSchema.toSchemaModel() adapter conversion.Added
Ack.enumCodec<T extends Enum>(List<T> values) returns a CodecSchema<String, T> wrapping EnumSchema<T>.NumberSchemaExtensions adds fluent numeric constraints to Ack.number(): .min, .max, .greaterThan, .lessThan, .positive, .negative, .multipleOf.Changed
Migration
double/num values. If a boundary must accept NaN/infinities, model that value outside the JSON numeric schema path before validation.ack_annotationsBreaking — Removed AckModel, AckField, and decorator annotations. Only @AckType() remains.
ack_generatorBreaking — Removed class-based schema generation. Only top-level @AckType() schema variables and getters are supported.
ack_firebase_aitoFirebaseAiResponseJsonSchema() for Firebase AI's GenerationConfig.responseJsonSchema path, plus committed golden fixtures and native fixture corpora.Schema conversion APIs — use toFirebaseAiResponseJsonSchema() instead.ack_json_schema_builderAckSchemaModel boundary and generic Draft-7 JSON Schema renderer; preserves defaults, const values, extension keywords, transformed metadata, and composition.All five packages are released in lockstep at 1.0.0-beta.12.
ack_generator now supports only
top-level @AckType() schema variables and getters.chore(release): bump to 1.0.0-beta.11
chore(release): bump to 1.0.0-beta.11 (#102)
docs: add ack package README for pub.dev
docs: add ack package README for pub.dev (#98)
chore(release): bump to 1.0.0-beta.9
chore(release): bump to 1.0.0-beta.9 (#88)
ack_json_schema_builder@1.0.0-beta.8
This release adds top-level enum/literal schema constructors, deprecates chained string schema methods, and improves the code generator's nested schem…
This release adds top-level enum/literal schema constructors, deprecates chained string schema methods, and improves the code generator's nested schema resolution.
Ack.enumString(), Ack.literal(), and Ack.enumValues() constructors for creating enum and literal schemas directly (#73)SchemaResult.map() for transforming validated valuesStringSchema.literal() and StringSchema.enumString() are deprecated — use Ack.literal() and Ack.enumString() instead (#74)| Package | Version |
|---|---|
| ack | 1.0.0-beta.7 |
| ack_annotations | 1.0.0-beta.7 |
| ack_generator | 1.0.0-beta.7 |
| ack_firebase_ai | 1.0.0-beta.7 |
| ack_json_schema_builder | 1.0.0-beta.7 |
refactor: deprecate withDescription in favor of describe by @leoafarias in https://github.com/btwld/ack/pull/46
Full Changelog: https://github.com/btwld/ack/compare/0.3.0-beta.1...v1.0.0-beta.6
schema.parseAs(...) / schema.safeParseAs(...) calls and stop emitting _$ackParse / _$ackSafeParse helpers.refactor: deprecate withDescription in favor of describe by @leoafarias in https://github.com/btwld/ack/pull/46
Full Changelog: https://github.com/btwld/ack/compare/0.3.0-beta.1...v1.0.0-beta.5
ack, ack_annotations, meta and test dependencies to latest versions (#56).Primitives: Comprehensive fixes for primitive schema generation and correctness.
Ack.list(schemaRef) for typed list getters (#47).REFACTOR: simplify validation workflow by eliminating duplicate nullable handling (#17).
* See release notes for details.
Multiple constraint classes have been deprecated in favor of unified ComparisonConstraint and PatternConstraint implementations:
melos api-check command replaces 19 complex shell commandsMultiple constraint classes have been deprecated in favor of unified ComparisonConstraint and PatternConstraint implementations:
String Constraints (use PatternConstraint instead):
StringDateTimeConstraint → PatternConstraint.dateTime()StringDateConstraint → PatternConstraint.date()StringEnumConstraint → PatternConstraint.enumValues()StringEmailConstraint → PatternConstraint.email()StringRegexConstraint → PatternConstraint.regex()StringJsonValidator → PatternConstraint.json()Numeric Constraints (use ComparisonConstraint instead):
NumberMinConstraint → ComparisonConstraint.numberMin()NumberMaxConstraint → ComparisonConstraint.numberMax()NumberRangeConstraint → ComparisonConstraint.numberRange()NumberExclusiveMinConstraint → ComparisonConstraint.numberExclusiveMin()NumberExclusiveMaxConstraint → ComparisonConstraint.numberExclusiveMax()NumberMultipleOfConstraint → ComparisonConstraint.numberMultipleOf()Collection Constraints (use ComparisonConstraint instead):
StringMinLengthConstraint → ComparisonConstraint.stringMinLength()StringMaxLengthConstraint → ComparisonConstraint.stringMaxLength()ListMinItemsConstraint → ComparisonConstraint.listMinItems()ListMaxItemsConstraint → ComparisonConstraint.listMaxItems()ObjectMinPropertiesConstraint → ComparisonConstraint.objectMinProperties()ObjectMaxPropertiesConstraint → ComparisonConstraint.objectMaxProperties()parse() and tryParse()All deprecated APIs remain functional with migration guidance. See the deprecations for detailed migration paths.
Full Changelog: https://github.com/btwld/ack/compare/v0.2.0-beta.1...0.3.0-beta.1
Packages with breaking changes:
Packages with other changes:
Packages with dependency updates only:
Packages listed below depend on other packages in this workspace that have had changes. Their versions have been incremented to bump the minimum dependency versions of the packages they depend upon in this project.
ack_example - v0.3.0-beta.2This release introduces significant improvements to the SchemaModel API, enhanced string validation, and better OpenAPI integration.
This release introduces significant improvements to the SchemaModel API, enhanced string validation, and better OpenAPI integration.
Annotate your models with validation rules:
@Schema()
class Product {
@IsNotEmpty()
final String id;
@MinLength(3)
final String name;
final double price;
final Category category;
Product({
required this.id,
required this.name,
required this.price,
required this.category,
});
}
Use the build_runner to generate schema classes:
dart run build_runner build --delete-conflicting-outputs
This creates a .schema.dart file with your generated schemas.
The constructor now validates data automatically:
// Create schema with automatic validation
final schema = ProductSchema({
'id': '123',
'name': 'Test Product',
'price': 19.99
});
// Check if valid
bool valid = schema.isValid;
Access validated data with type-safe getters:
// Type-safe access to properties
String id = schema.id;
String name = schema.name;
double price = schema.price;
// Access nested schema objects
CategorySchema category = schema.category;
String categoryName = category.name;
Get detailed error information when validation fails:
if (!schema.isValid) {
SchemaError? error = schema.getErrors();
// Error details
String errorType = error?.name; // e.g., "required_field"
String message = error?.message; // e.g., "Required field is missing"
String? path = error?.path; // e.g., "category.id"
}
Transform schema data to strongly-typed models:
// Convert schema to model instance
Product product = schema.toModel();
// Access model properties
String id = product.id;
Category category = product.category;
Choose your preferred validation style:
// Approach 1: Constructor + isValid check
final schema = ProductSchema(data);
if (schema.isValid) {
final product = schema.toModel();
}
// Approach 2: Direct parse (throws on failure)
try {
Product product = ProductSchema.parse(data);
} catch (e) {
// Handle validation error
}
// Approach 3: Try-parse (returns null on failure)
Product? product = ProductSchema.tryParse(data);
if (product != null) {
// Use valid product
}
Convert model instances to schemas for serialization:
// Create schema from model instance
final schema = ProductSchema.fromModel(product);
// Serialize to various formats
Map<String, Object?> map = schema.toMap();
String json = schema.toJson();
The matches() method now validates entire strings:
// Full string pattern matching (with anchors)
final schema = Ack.string.matches('^[a-z0-9_]{3,16}$');
schema.validate('user_123').isOk; // true
schema.validate('user@123').isOk; // false - contains @
New contains() method for substring matching:
// Partial string matching
final schema = Ack.string.contains('important');
schema.validate('This is important text').isOk; // true
schema.validate('Nothing here').isOk; // false
Generate API specifications from your schemas:
// Get JSON Schema
Map<String, Object?> jsonSchema = ProductSchema.toJsonSchema();
// Convert to JSON string
String jsonString = jsonEncode(jsonSchema);
If you're upgrading from 0.1.x, note these changes:
Update string pattern validation:
// Old (0.1.x): Matches substrings
Ack.string.matches('abc'); // Would match 'abcdef'
// New (0.2.0): Matches whole string
Ack.string.matches('^abc$'); // Only matches 'abc' exactly
Ack.string.contains('abc'); // Matches substrings, like old matches()
Use the new validation workflow:
// Create and validate in one step
final schema = ProductSchema(data);
// Check isValid before using
if (schema.isValid) {
schema.id; // Access schema properties
schema.category.name; // Access nested properties
// Or convert to model
final product = schema.toModel();
}
Full documentation is available at https://docs.page/btwld/ack
0.2.0-beta.1.Packages with breaking changes:
Packages with other changes:
One column per month.