Changelog

What changed in Vera, newest first. Dates are when the change landed on main.

This page is a committed file (docs/changelog.md), not a feed generated from commit messages: a commit log records every change, and a changelog records the ones a customer can tell the difference between. Entries are grouped by the question they answer — is this new, is this a fix, does it change how something already behaves.

Something behaving differently and not listed here? That is a bug in this page as much as anywhere else — tell us via the contact page and we will correct it.

---

2026-08-20

Reliability

• A redelivered job can no longer run twice. Queued runs are now claimed under a renewable lease, so if a worker is killed mid-run the job is picked up by another worker rather than executed twice or stranded in running forever.
• Runs have a wall-clock ceiling. A run that hangs is now stopped and reported rather than holding a browser indefinitely.
• Deploys drain in-flight runs. A restart waits for running tests to finish writing their results instead of killing them mid-write.
• /api/health/ready reports real dependencies. Database, schema version, queue and live workers are each checked, so "the API answers" and "the API can actually take work" stopped being the same signal.

Billing

• A failed card no longer looks like a cancellation. A payment retry (past_due) keeps the workspace on its plan while the provider retries; the downgrade happens only when the subscription actually ends. Previously the first failed charge dropped the workspace to Free immediately.
• Plan changes are explained. When a workspace changes plan — in either direction — its admins get an email stating what changed about the workspace: concurrency, retention, and which features moved. A downgrade notice says explicitly that projects, tests and history are unchanged.

Consumption

• Usage is visible before it is enforced. Settings → Billing now shows runs, run minutes and artifact storage for the current period against the plan's allowance, and warns at 70/90/100% — once per period per limit, in-product and by email.

Workspaces

• Self-service closure. A workspace can be closed from Settings, with a grace period before its data is purged, and exported first.

---

2026-08-19

Testing

• Assertion sensitivity works on any test, not only dataset-backed ones. A test can now be checked for whether its assertions would actually catch a regression, regardless of how it was authored.
• /proof — a public page explaining what Vera's coverage claims do and do not mean.

Fixes

• Pricing cards no longer omit two features the plans include.
• The Enterprise card no longer advertises self-hosting.

---

2026-08-18

Local agent

• vera-agent runs project setup actions on leased runs, so a test that depends on seeded fixtures behaves the same locally as in the cloud.
• Capability scopes on agent tokens — an agent token can be limited to what that machine is allowed to do, and the agent reports any capability it had to drop rather than silently degrading.
• Visual regression works for agent runs.

Privacy

• Self-heal DOM snapshots are redacted before leaving the machine. The snapshot Vera sends to repair a broken selector no longer carries input values.
• Published what Vera stores and where it goes — see data handling.

Operations

• Optional error reporting (Sentry), budgeted so it cannot run away on the free plan.
• Operator email on new signups.