v0.9.0

v0.9.0 (2026-05-14)

⚠ BREAKING CHANGES

• config: nest repository settings under per-provider sub-sections (fd49da6)

Features

• config: nest repository settings under per-provider sub-sections (fd49da6)

Migration Notes

• Repository config schema is restructured. The flat repository fields (host, owner, repo, project, organization, collection) have been moved under per-provider sub-sections: repository.github, repository.gitlab, and repository.azuredevops. Only the sub-section matching the top-level provider may be set; provider: auto allows no sub-section at all. Old configs fail to load with a "field not found" parse error pointing at the legacy key. Migrate .yeet.yaml as follows:

  # before
  provider: github
  repository:
    host: github.com
    owner: acme
    repo: widgets
  
  # after
  provider: github
  repository:
    github:
      host: github.com
      owner: acme
      repo: widgets

  # before
  provider: gitlab
  repository:
    host: gitlab.company.com
    project: group/sub/widgets
  
  # after
  provider: gitlab
  repository:
    gitlab:
      host: gitlab.company.com
      project: group/sub/widgets

  # before
  provider: azuredevops
  repository:
    host: dev.azure.com
    organization: contoso
    project: MyProject
    repo: widgets
  
  # after
  provider: azuredevops
  repository:
    azuredevops:
      host: dev.azure.com
      organization: contoso
      project: MyProject
      repo: widgets

• CLI flags are stricter. Repository field flags (--host, --owner, --repo, --project) now require an explicit --provider (or provider: in config). --owner/--repo are valid only for --provider github. --owner is rejected for --provider azuredevops.