Depot 0.0.0

Caution

This is an example, not a release. Depot 0.0.0 does not exist, and nothing on this page describes a real change. It is here so that the release list, the layout and the fixed anchors can be checked before the first real note is published. Delete it then.

Everything below is the shape a Depot release note takes. The seven headings and their anchors are fixed, so that a link to #security or #upgrade-notes keeps working across every release.

Highlights

• The change most people will notice. One sentence on what it does for the reader, then a link to the page that explains it. See operating modes.
• The second one. Same shape. Two or three of these, no more.

Added

• What is now possible that was not possible before, written from the reader’s side rather than the implementation’s.

Changed

• What used to happen, and what happens now. The old behaviour is named because that is what the reader remembers.

Fixed

• The symptom that no longer happens, described the way somebody hitting it would have described it.

Security

• Severity. What was wrong, what an attacker would need, and what they could do. If a deployment is exposed without the fix, the note says so here rather than in the highlights.

Known issues

• KI-0000. The symptom and the workaround, with the identifier so that a support conversation can name it. See known issues.

Upgrade notes

No action is needed beyond installing this version.

This heading is never deleted. A reader looking for it and not finding it assumes the note is incomplete, so a release with nothing to do says so.