> For the complete documentation index, see [llms.txt](https://swappulse.gitbook.io/swappulse-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://swappulse.gitbook.io/swappulse-docs/changelog/v0-6-0.md).

# SwapPulse v0.6.0: Automated GitHub release discipline

Full release notes for SwapPulse v0.6.0.

This release establishes the versioning/release process itself.

## New release infrastructure

* [changelog](https://swappulse.gitbook.io/swappulse-docs/changelog) with preserved milestone history in oldest-to-newest order.
* `RELEASE_MANIFEST.json` as the machine-readable source of official versions.
* Dedicated [versioned release notes](https://swappulse.gitbook.io/swappulse-docs/changelog) release notes.
* GitHub Actions publisher that creates missing GitHub releases from the manifest after changes reach `main`.
* Release policy for future website, backend, AT Protocol and chain updates.

## Historical releases

The first five releases are backfilled only from preserved checkpoint commits. Earlier development history is intentionally left as Git history rather than receiving invented version numbers.

## Release-note standard

Future significant releases must describe:

* new features;
* updated components/behaviour;
* removed or deprecated functionality;
* rationale;
* security/privacy implications;
* localisation/accessibility impact;
* deployment or migration requirements;
* tests/checks completed.

## Licensing documentation

This release also documents candidate open-source licences and the separation between SwapPulse-owned source code and third-party material/services such as TCGdex data/SDKs and Pokémon intellectual property.

## Why

A regular release record gives users and contributors a dependable way to understand what changed and why. It also makes forks easier to maintain and gives security-sensitive changes a visible audit trail outside individual Git commits.