# Switchyard changelog

> What changed for people and agents who use Switchyard, newest first, each with its date, its kind and who it is for. The Atom feed is at https://switchyard.so/changelog/feed.xml; the docs are listed at https://switchyard.so/llms.txt

## yard 0.2.15 names the issue a task serves

- date: 2026-11-20
- kind: added
- audience: cli
- yard: 0.2.15
- address: https://switchyard.so/changelog/2026-11-20-yard-0-2-15.md

A task can name the issue it serves in your tracker, and yard writes the id where Linear, Jira and GitHub already look for it. The flags are in the [command reference](/docs/cli).

- `yard branch new "<goal>" --issue <ID>` names the issue the task completes, such as `ENG-123` or a GitHub issue's number after `#`. `--part-of <ID>` names an issue the task contributes to. They are kept as the tags `issue` and `part-of`, and `yard tag` changes them later.
- `yard status` shows the issue before the task: `ENG-123 · task 8`.
- `yard commit` adds `Fixes <ID>` or `Part of <ID>` to the commit message, in a paragraph of its own above the commit's trailers, unless the message already names the id. yard learns a task's id when the task is made with these flags, and from `yard status` or `yard tag` run in that checkout.

## yard 0.2.14 asks before it ends access, and says when a newer yard is out

- date: 2026-11-19
- kind: changed
- audience: cli
- breaking: true
- yard: 0.2.14
- address: https://switchyard.so/changelog/2026-11-19-yard-0-2-14.md

Six commands that end access or discard what cannot be got back now ask first, and six organization commands that a person finishes in a browser now exit 8. Both change what a script sees. The rest of this release adds commands and makes yard clearer at a terminal. Every command is in the [command reference](/docs/cli).

### Who is affected

- A script or an agent that runs `yard branch key`, `yard group <id> revoke`, `yard org key revoke`, `yard webhook remove`, `yard resolutions forget` or `yard notifications clear --all`. From 0.2.14 these ask before they act. A person at a terminal answers y. Where there is no terminal, or with `--json`, the command sends nothing, exits 1 with the error code `input_needed`, and its hint names the exact command to run.
- A script that reads the exit status of `yard org ai-fixes on|off`, `yard org agent-approvals on|off`, `yard org engine-sizing grows`, `yard org delete`, `yard org secret` or `yard org limit set`. These acts are done by a person in a browser. yard printed the page's link and exited 0, as if the act were done. It now answers `approval_required` with the link in the hint and exits 8, as every other act a person does in a browser does.

### What to do

- Add `--yes` to each of the six commands a script or an agent runs. `yard notifications clear` with named ids, a project or a task never asks and needs no change.
- Treat exit 8 from the six organization commands as "a person must finish this in a browser", and show them the link from the hint.
- Pass a device code to `yard login <url> --complete -` on stdin. A code given as the argument still works, with a warning, since shell history and the process list keep it.

### Added

- `yard notifications`: what needs you and what is for your information, with `read`, `clear`, `mute`, `unmute` and `settings`.
- `yard queue health`: the merge queue's health in one sentence, the one thing that needs a person, how long submit to merged takes, how many tasks wait and the share sent back. See [queue health](/docs/queue-health).
- `yard priority`: merge a queued task in the priority lane, after hotfixes and before the normal lane. See [merge lanes](/docs/merge-lanes).
- `yard pr status <pull>`: where a pull request stands in the merge queue. See [pull requests](/docs/pull-requests).
- `yard value` and `yard org value <org>`: what Switchyard did for a project or an organization over 1, 7 or 30 days.
- `yard webhook test <id>` sends one test event to an endpoint and prints its result. `yard webhook verify` checks a delivery's signature on your machine, with no network and no sign-in. See [webhooks](/docs/webhooks).
- A notice when a newer yard is out: one line on stderr after a command, at most once a day, naming the command that updates it. It shows only at a terminal, never with `--json` and never where `CI` is set. Set `YARD_NO_UPDATE_CHECK` to turn it off.
- An example in the `--help` of the 56 commands that had none, the same line the command reference shows.

### Changed

- `yard` with no command prints the four first steps in the order that works.
- `yard doctor` before you have signed in exits 0 and names the command that signs you in. Not signed in and no project are warnings, so a script reads each check's status.
- `yard login <url> --complete -` at a terminal asks for the device code and reads it with echo off. It used to wait silently for the end of input.
- `yard login <url> --github` says how long the code lasts while it waits.
- `yard --help` no longer lists `yard github`, which only Switchyard's own team can use.
- Progress while yard waits is said in plain lines on a terminal that sets `TERM=dumb`, with no spinner.
- `yard account agents end` says the agent's keys stop working.

### Fixed

- A submit answered 503 with its outcome not known is sent again by yard and lands.
- `yard org card` shows a Link payment method by its label, with no expiry.

## Switchyard has a changelog

- date: 2026-11-17
- kind: added
- audience: api
- address: https://switchyard.so/changelog/2026-11-17-changelog.md

Changes to Switchyard are now listed at [switchyard.so/changelog](/changelog), newest first, each with its date, its kind and who it is for. To follow them, add the [Atom feed](/changelog/feed.xml) to a feed reader; an agent can read every entry as Markdown at [changelog.md](/changelog.md), and the [introduction](/docs/introduction#how-to-read-these-pages) to the docs links the list. The list starts with this entry: changes made before it are not written back.
