anentropic/chuckd schema compatibility check

Validate schema evolution compatibility using chuckd

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit Mar 17, 2026
License: MIT

Pinned Snippet

workflow.ymlSHA-pinned

uses: anentropic/chuckd-action@dd62d33d0f3d78cfb426b1d3eb24b468ace7d6ec # no releases — HEAD as of 2026-07-12

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
schema-pattern	Glob pattern matching schema versions (e.g. "schemas/person.*.json"). Mutually exclusive with schema-file.	no	""
schema-file	Path to the new schema file (for explicit-path or git-compare mode). Mutually exclusive with schema-pattern.	no	""
previous-schemas	Space or newline-separated paths to previous schema versions (explicit-path mode)	no	""
format	Schema format: JSONSCHEMA, AVRO, or PROTOBUF	no	JSONSCHEMA
compatibility	Compatibility mode: BACKWARD, FORWARD, FULL, BACKWARD_TRANSITIVE, FORWARD_TRANSITIVE, FULL_TRANSITIVE	no	BACKWARD
log-level	Log level: DEBUG, INFO, WARN, ERROR	no	WARN
output-format	Output format for chuckd results: TEXT or JSON	no	TEXT
version	chuckd version to download (e.g. 1.0.2). Defaults to latest compatible.	no	""
base-ref	Base branch/ref for git-compare mode	no	""
github-token	GitHub token for API requests	no	${{ github.token }}

Outputs

name	description
exit-code	chuckd exit code: 0=compatible, 1=incompatible, 2=usage error, 3=runtime error