v0.28.7

What's New

Bug Fixes

• Released the landmark crate from crates.io now reports honestly: earlier releases marked publication as successful while the crate was actually skipped, so three versions shipped without reaching the registry. The no-op job is removed, and crates.io publishing will return only as a deliberate, explicit step.
• The release gate's semantic-release dry-run proof now exits with a clear failure when anything goes wrong, instead of quietly passing with swallowed errors, so dependency-major problems get caught before merge.

Release classification notes

Landmark classification notice: deterministic release signals (conventional:chore, conventional:fix, dependency) disagreed with model classification; synthesis proceeded. deterministic floor found user-visible commit signals but model did not; deterministic floor prevented low-significance skip

0.28.7 (2026-08-23)

Bug Fixes

• gate: make the semantic-release dry-run proof fail loudly (#249) (e33c216)

v0.28.6

What's New

New Features

• Release notes are now composed and validated before a release ships, so published releases carry complete, polished write-ups instead of temporary placeholders or technical-only bodies.
• Pending release decisions and their notes can be previewed locally with a new dry-run flag, and publication fails fast if the notes are missing or blank.

Bug Fixes

• Maintenance-only releases (for example, dependency upgrades) are no longer classified as user-visible, so they're correctly skipped instead of producing contradictory changelog notes.
• Mixed-scope wrapper commits no longer cause misclassification: each conventional entry is classified against the scope of its own line, keeping same-type changes with opposite scopes distinct.
• Changelog section detection now recognizes both # and ## headings and matches version numbers exactly, ensuring Landmark can find its own release entries that use compare-URL-based headings.

Release classification notes

Landmark classification notice: deterministic release signals (conventional:chore, conventional:feat, conventional:fix, conventional:fix(maintenance-scope), security) disagreed with model classification; synthesis proceeded. deterministic floor found security signals but model did not

0.28.6 (2026-08-23)

Features

• self-release: synthesize notes before publication; compose once (#247) (ebd2619)

Bug Fixes

• classification: maintenance scopes are not user-visible; extract H1 changelog sections (#244) (e129c05)
• classification: classify each conventional entry against its own scope (#246) (33f2a49)

v0.28.5

0.28.5 (2026-08-22)

Bug Fixes

• deps: restore canonical Hmac::new_from_slice construction (#242) (410e5a1)

v0.28.4

0.28.4 (2026-08-22)

Features

• gate: enforce dependency and model-pin freshness (bfd2fd9)

v0.28.3

What's New

New Features

Fresh model pins for each tier now land on fast, low-cost DeepSeek models, with Gemini in the fallback path — net cost drops while existing manifest overrides still win.
Budget estimation now uses current DeepSeek/Gemini rates, so gate calculations match real provider pricing.

Bug Fixes

model.policy in a manifest is now case-insensitive; writing OFF on uppercase variants no longer trips validation. The published manifest schema now mirrors that same case tolerance, so schema-aware tools agree with the CLI.

Release classification notes

Landmark classification notice: deterministic release signals (conventional:chore, conventional:docs, conventional:feat, conventional:fix, migration) disagreed with model classification; synthesis proceeded. deterministic floor found migration signals but model did not

0.28.3 (2026-08-21)

Features

• model-policy: repin all tiers to commodity DeepSeek/Gemini models (#218) (90dce6f)

Bug Fixes

• manifest: accept any case for model.policy (#220) (037d2a9)
• schema: make manifest model.policy case-insensitive (#221) (2938de9)

v0.28.2

0.28.2 (2026-07-14)

Features

• prepare and bind atomic release transactions (#215) (a28a590)

v0.28.1

What's New

Bug Fixes

• Newly generated fleet workflows and templates were still pinning to landmark@v1, which could silently reintroduce the old pre-stable version line on new adoptions; all generators, templates, and docs now correctly reference landmark@v0.
• Generated release workflows previously pointed users toward a custom GH_RELEASE_TOKEN; guidance now points to the default workflow token, since generated jobs already include the necessary permissions block.

Release classification notes

Landmark classification notice: deterministic release signals (conventional:chore, conventional:fix, conventional:test, migration) disagreed with model classification; synthesis proceeded. deterministic floor found migration signals but model did not

0.28.1 (2026-07-09)

Bug Fixes

• fleet: generate and document landmark@v0 + workflow-token releases (#207) (f5162bb)

Version reset: 1.28.0 → 0.28.0 (2026-07-08)

The fleet moved to pre-stable 0.x semantics (landmark-016). The 1.x line was
renumbered to 0.x with the same content: v1.28.0 == v0.28.0 (commit
80ce543). Pre-1.0 bumps follow Cargo-style semver — breaking changes bump
the minor version, features and fixes bump the patch version. 1.0.0 will
only ever be tagged deliberately, once the API is ready to commit to
stability.