Release v0.1.0

REST 0.1.0 is a breaking release using published Core and Bundle 0.1.0.

Migrate labels to target: {resource_type, attribute}, adopt format 2 bundle/module manifests, rebuild archives, and re-sign. Replace legacy health/OpenAPI endpoints with /livez, /readyz, and /openapi.json. Policy versions require hash, timestamp, nullable label identifier, and unsigned generation; schema revisions remain separate. Upgrade consumers to the strict current contract. Invalid replacement configurations leave the prior authorization generation active.

See the migration guide for concrete updates.

Release v0.0.16

REST 0.0.16 adopts Core 0.0.25 and Bundle 0.0.7.

• Each authorization batch evaluates one frozen policy, schema, and label state.
• Policy versions include nullable label_set and unsigned generation; generation is local to one engine instance and can restart on replacement.
• Invalid label reloads fail before publication and preserve the prior active state. Rules on disjoint resource kinds can share an output through one runtime owner; duplicate destinations within one kind remain invalid.
• Breaking: malformed identities and IP values now fail JSON deserialization with HTTP 400 for the whole batch. Correct those inputs instead of expecting a per-item evaluation error.
• Existing Allow/Deny response shapes remain stable. Rebuild and re-sign Bundle archives with CLI 0.0.7 before deploying them.

The migration passed 45 checks, including 37 instruction-level benchmarks with no gated regressions. The version-only release passed all 45 checks with 37 neutral benchmarks.

See migration #71, release #72, and the changelog.

Release v0.0.15

Release treetop-rest 0.0.15

Release v0.0.14

Release treetop-rest 0.0.14

Release v0.0.13

treetop-rest 0.0.13

Release v0.0.12

treetop-rest 0.0.12

Release v0.0.11

treetop-rest v0.0.11

Release v0.0.10

Release v0.0.10

Release v0.0.9

Release v0.0.9

Release v0.0.7

Release v0.0.7