v0.2.1

Release Notes for v0.2.1

Highlights

• Ships the post-0.2.0 hardening batch on main: ADR-041 tiered object-storage orchestration event-log work, deterministic local pipeline UAT, and deployed-UAT readiness/provenance guardrails.
• Hardens orchestration correctness across dispatch envelopes, task tokens, callback idempotency, compaction, retry recovery, pagination stability, and unknown-event tolerance.
• Tightens catalog, Iceberg, and Unity Catalog protocol behavior around idempotency, credential-vending scope, public-route rate limiting, sanitized storage errors, thrift allocation bounds, and JWT feature compatibility.
• Updates public API contract coverage, generated OpenAPI metadata, crate documentation, architecture boundary docs, and Batch 7 catalog I/O/write-amplification baselines for the 0.2.1 line.
• Keeps live deployed UAT as a gated evidence requirement: this release includes readiness/provenance tooling, not a claim that deployed UAT proof has been collected.

Changelog Reference

• Change log entry: 0.2.1

Verification

• Local release-doc discipline check: bash tools/check-release-tag-discipline.sh --tag v0.2.1
• Release-prep metadata check: bash tools/test_release_prep_v0_2_1.sh
• Release gate checklist: cargo xtask doctor, cargo xtask verify-integrity, cargo xtask repo-hygiene-check, cargo xtask adr-check, cargo xtask parity-matrix-check, cargo xtask proto-breaking-check, cargo xtask ci-parity, and cargo xtask uc-openapi-inventory.
• Workspace gate checklist: cargo check --workspace --all-features, cargo test --workspace --all-features --exclude arco-flow --exclude arco-api, and targeted arco-flow / arco-api parity/API gates.
• Documentation and contract checklist: mdbook build docs/guide, buf lint proto/, and checked-in OpenAPI regeneration from arco-api.

Arco 0.2.0

Arco 0.2.0

Arco 0.2.0 is the control-plane contract cut.

This release intentionally breaks from the 0.1.x API shape so Arco can stabilize the catalog, metastore, governance, and orchestration contracts around the surface we want to support going forward. If you generate protobuf or OpenAPI clients, call orchestration callback APIs, or depend on the older catalog/control-plane shapes, treat this as a breaking upgrade.

The main change is that Arco now has a real expanded control-plane surface: scoped metastore mutations, catalog product APIs, Unity Catalog compatibility inventory, tenant-visible system-table contracts, root transactions, task-token callbacks, worker dispatch envelopes, and output visibility lifecycle coverage.

Breaking Changes

• The public proto/OpenAPI contract has moved to the post-hard-cut arco.*.v1 baseline.
• Pre-0.2 generated clients should be regenerated.
• Integrations using older catalog, metastore, orchestration, or callback shapes need to be reviewed against the new contracts.
• Release tooling now expects Rust 1.88 and Buf 1.70.0.

What Shipped

• Catalog control-plane APIs for scoped metastore mutations and catalog product surfaces.
• Unity Catalog compatibility inventory and support-registry coverage.
• Tenant-visible system-table contracts.
• Orchestration contracts for root transactions, task-token callbacks, worker dispatch, and output visibility.
• Stronger release gates for CI parity, repo hygiene, integrity checks, proto compatibility, and signed release tags.
• A Tier-1 catalog snapshot retry fix that accepts byte-identical immutable snapshot retries while still rejecting divergent content.

Upgrade Notes

Regenerate clients, bump Rust/Python dependencies to 0.2.0, and retest catalog and orchestration workflows before deploying. This release is the point where the expanded arco.*.v1 contract becomes the baseline for future additive changes.

v0.1.5

v0.1.5

v0.1.4

v0.1.4

v0.1.3

Release Notes for v0.1.3

Highlights

• Corrected release-tag signature verification behavior in the GitHub-hosted SBOM workflow by using a verified tagger identity for signed release tags.

Changelog Reference

• Change log entry: 0.1.3

Verification

• Release-tag CI discipline is enforced by .github/workflows/ci.yml (Release Tag Discipline job).
• SBOM publication + retention + provenance attestation are enforced by .github/workflows/release-sbom.yml.
• Immutable release artifact pack is generated by tools/collect_release_evidence.sh and uploaded by the SBOM workflow.

v0.1.2

Release Notes for v0.1.2

Highlights

• Fixed release SBOM CI wait behavior to poll commit check-runs for Release Tag Discipline, preventing false timeout failures on tag-triggered releases.

Changelog Reference

• Change log entry: 0.1.2

Verification

• Release-tag CI discipline is enforced by .github/workflows/ci.yml (Release Tag Discipline job).
• SBOM publication + retention + provenance attestation are enforced by .github/workflows/release-sbom.yml.
• Immutable release artifact pack is generated by tools/collect_release_evidence.sh and uploaded by the SBOM workflow.

v0.1.1

Release Notes for v0.1.1

Highlights

• Added Gate 1 release-discipline hardening across signed-tag checks, immutable release-evidence collection, and release-tag CI/SBOM enforcement artifacts.

Changelog Reference

• Change log entry: 0.1.1

Verification

• Release-tag CI discipline is enforced by .github/workflows/ci.yml (Release Tag Discipline job).
• SBOM publication + retention + provenance attestation are enforced by .github/workflows/release-sbom.yml.
• Immutable release artifact pack is generated by tools/collect_release_evidence.sh and uploaded by the SBOM workflow.