v0.30.0

🚀 Features

• (app) Propagate tickets config onto content drivers - (10410fa) by @bchatard

  withEnvDerivations now carries cfg.Tickets onto the changelog/release-notes driver
  clones (the same clone point as remote_metadata), so the gitcliff generator can
  inject link_parsers. Part of T80.

  Co-Authored-By:Claude Opus 4.8 noreply@anthropic.com

• (config) Add tickets field for issue-tracker links - (770c318) by @bchatard

  Top-level tickets list ([]Ticket{Pattern, URL}) parsed from .heraut.yml, plus the
  programmatic ContentDriver.Tickets carrier the app layer will populate. Part of T79.

  Co-Authored-By:Claude Opus 4.8 noreply@anthropic.com

• (config) Validate tickets (regex, {ticket} url, git-cliff only) - (a159801) by @bchatard

  validateTickets:each pattern compiles as a regex, each url is an absolute http(s)
  URL containing {ticket}, and tickets require the git-cliff generator (the only one
  with a link mechanism). Part of T79. Co-Authored-By:Claude Opus 4.8 noreply@anthropic.com

• (config) Add tickets to schema + sample + fixtures - (0de6706) by @bchatard

  Expose the tickets array in schema.json (pattern + url, both required), document
  it in docs/heraut.sample.yml, and add valid + invalid schema fixtures (the invalid
  one omits the required url). Part of T82.

  Co-Authored-By:Claude Opus 4.8 noreply@anthropic.com

• (generators/gitcliff) Inject ticket link_parsers into effective config - (cc1925d) by @bchatard

  effectiveConfig now chains injectLinkParsers after the heading postprocessor: each
  ticket becomes a git-cliff { pattern, href } entry — pattern wrapped in a capture
  group only when it has none (so {ticket}->$1 is the URL value), appended to any
  existing [git].link_parsers. Part of T80.

  Co-Authored-By:Claude Opus 4.8 noreply@anthropic.com

• (generators/gitcliff) Render ticket links in changelog and release notes - (98f83e1) by @bchatard

  Both print_commit macros append commit.links after the PR segment as
  ( TICKET ). Verified against the real git-cliff: subject and footer (Refs:)
  tickets both render with clean whitespace, location-independent. Part of T81.

  Co-Authored-By:Claude Opus 4.8 noreply@anthropic.com

📚 Documentation

• (plans) Add ticket-linking design spec - (6dee113) by @bchatard

  Approved brainstorming design: first-class .heraut.yml ticket linking via a
  top-level tickets list, injected into git-cliff's link_parsers (location-
  independent — subject/body/footer), rendered in both changelog and release notes.
  git-cliff only; append-only; {ticket} maps to the first capture group (or full
  match) so label vs URL value can differ (e.g. GH-123 → /issues/123).

  Co-Authored-By:Claude Opus 4.8 noreply@anthropic.com

• (plans) Add ticket-linking implementation plan - (d33f307) by @bchatard

  Seven TDD tasks (config field, validation, link_parsers injection, driver
  propagation, both templates, schema/sample/fixtures, ADR/spec/roadmap) for T79,
  each with failing test, implementation, and commit steps.

  Co-Authored-By:Claude Opus 4.8 noreply@anthropic.com

• (roadmap) Add Phase 15 — ticket linking (T79–T82) - (dfc44c5) by @bchatard

  New phase tracking the ticket-linking feature: config surface + validation (T79),
  link_parsers injection + driver propagation (T80), template rendering (T81), and
  schema/sample/ADR/spec (T82).

  Co-Authored-By:Claude Opus 4.8 noreply@anthropic.com

• ADR-0024 ticket linking; document tickets; complete T79–T82 - (485c07a) by @bchatard

  Record the link_parsers-over-commit_preprocessors decision (ADR-0024), document the
  tickets config in spec 02, and flip Phase 15 (T79–T82) to done with completion notes.

  Co-Authored-By:Claude Opus 4.8 noreply@anthropic.com

Commit Statistics

• 10 commit(s) contributed to the release.
• 0 day(s) passed between the first and last commit.
• 10 commit(s) parsed as conventional.
• 0 linked issue(s) detected in commits.