Changelog
Most product changelogs are marketing. This one exists for a narrower reason: a scanner sits inside your pipeline, and some of our changes can turn a build red without a line of your code moving. Those are written down here, whether or not they are flattering.
Nothing has been released yet
Skiplink is in pre-release. The hosted API is not deployed, the packages are not on npm and no version has ever run in anybody's CI, so there is nothing to report and this page says so rather than opening with a fabricated 1.0.
Entries appear here newest first from the first release onwards. Whether the API is answering right now is a separate question.
What is pinned today
| Thing | Version | Where you see it |
|---|---|---|
| axe-core | 4.12.1 |
Returned on every scan result, so a finding can always be attributed to an engine version. |
| Baseline file format | 1 |
.skiplink/baseline.json. The CLI refuses a file whose version it does not read, rather than guessing at it. |
| API | v1 |
Every endpoint is under /v1/. |
What always gets written down
- A change of axe-core version
- The engine is pinned, not floated. A new version can find things the old one did not, which reads to you as a regression we caused unless we say otherwise — so the version ships inside every result and a bump is recorded here.
- Anything that changes violation identity
- Violations are fingerprinted, and a baseline is a list of fingerprints you have accepted. Change how identity is computed and every baseline in the field goes stale at once: every customer's next build fails, having changed nothing. It is the most expensive change we can make and it gets the loudest entry.
- Breaking API changes
- Anything that would make a working integration stop working — a removed field, a changed error code, a stricter parameter.
- Price changes
- Recorded here and emailed with at least 30 days' notice, and never applied to a period already paid for. That is §7 of the terms, not a courtesy.
How you find out without reading this page
A changelog only works for people who read changelogs, so the two changes that can break a build announce themselves in the pipeline instead:
- The engine version is in every scan result. Diff two results and the engine is right there beside the findings.
- The baseline file carries its own format version, and a CLI that does not read that version says so and stops — rather than reading it optimistically and reporting a green gate over a file it misunderstood.
Neither is a substitute for telling you. Both exist because the alternative is a customer discovering a change from a red build at four in the afternoon.