deployangel (Python) 0.1.26

• deployangel doctor warns when the project's AGENTS.md or CLAUDE.md has
  an older copy of the block deployangel install agents writes, and
  deployangel status says so on stderr at the start of a session, where
  a coding agent reads it. Running deployangel install agents updates
  it. Hand-written instructions without the block's markers aren't
  checked. Matches the Ruby gem.

deployangel (Python) 0.1.25

• deployangel verify shows a volume drop (servers from 2026-11-04) as
  what ran against what was expected (0 requests, about 27 expected),
  and lists findings a person accepted as an intended change, with who
  and why. A failing finding that could be intended gets the link where a
  person can accept it; the CLI and MCP server can't, so an agent never
  accepts its own failure.
• The MCP server's instructions, and the block deployangel install agents writes, tell agents to hand that link to the user with their
  evidence and never report the release as a success.

deployangel (Python) 0.1.24

• An exception raised entirely in packages, with no frame from the app's
  code, now sends its first library frames as its stack trace
  (django/core/mail/backends/smtp.py#open), normalized like the top
  frame, with no absolute paths or versions. Before, it sent none, so an
  error such as an email task's SMTP timeout showed no trace. Matches the
  Ruby gem.

deployangel (Python) 0.1.23

• deployangel exercise --param pk=42 fills path parameters (<int:pk>,
  {pk}, :pk), so routes with IDs in their paths can be exercised.
  Skipped routes name the parameters they need.
• deployangel exercise --header="Name: value", or
  DEPLOYANGEL_EXERCISE_HEADERS (one per line), sends headers with every
  request, such as a Bearer token or a test account's session cookie. The
  output names them but never shows their values, and they go only to the
  --url host. Matches the Ruby gem.

deployangel (Python) 0.1.22

• deployangel exercise prints each route's status codes (404 ×1)
  instead of their class (1 4xx). When every page answers 404, 405, or
  410, as when --url is the app's marketing site rather than its own
  host, it says so, records nothing on the release, and exits 5. Matches
  the Ruby gem.

deployangel (Python) 0.1.21

• deployangel verify prints a failed release's next steps: the last
  cleared release a rollback would go to, with the migrations it would
  cross, and where to look first. They come from the verdict document's new
  next_steps field, so servers before 2026-11-01 show none. The coding
  agent instructions mention them, and still say to ask before rolling back.

deployangel (Python) 0.1.20

• deployangel mcp starts without an API token. Each tool then answers with
  how to set DEPLOYANGEL_API_TOKEN (or run deployangel setup), instead of
  the server failing to start, which many coding agents only report as
  "failed to start".

deployangel (Python) 0.1.19

• The MCP server is listed in the official MCP Registry as
  com.deployangel/deployangel, a name proven by deployangel.com's DNS.

deployangel (Python) 0.1.18

• The MCP server is listed in the official MCP Registry as
  io.github.DeployAngel/deployangel, so MCP clients and directories that read
  the registry can find and install it (uvx deployangel mcp). The README
  carries the registry name, which is how the registry confirms the package is
  ours.

deployangel (Python) 0.1.17

• The instructions deployangel install agents writes to AGENTS.md now tell
  coding agents to check recent releases and late regressions at the start
  of a session, and to read fix_check in the verdict after deploying a fix
  for a failed release. Run it again to update them.