Release checklist

Work through this list after each ISO release, including ISO refreshes.

1. Release history. Add the release to Release history. Use the creation date of the announcement post, not its last update.

2. Changelogs. When the release changelog moves into Past changelogs/ in the changelogs repository, add it to Changelogs. Keep the upcoming row as “Next release, date not set”. The date in Upcoming.md is only the date the changelog was built.

3. Apps. Compare the Garuda apps index with the replaces list in the garuda-toolbox PKGBUILD, with archive/PKGBUILD/ and with the changelogs. Remove pages of apps that were replaced, merged or deprecated.

4. Editions. Compare the edition table in Installation instructions with the folders in iso-profiles/garuda/ and iso-profiles/community/.

5. Defaults. Check the default kernel, login manager, browser and shell in the iso-profiles package lists and profile.conf files. Update every page that names them.

6. Screenshots. Retake the screenshots in the screenshot list that show a changed screen, theme or release name.

7. Cheat sheets. Compare the cheat sheets with the shipped configs in the garuda-*-settings repositories and garuda-fish-config.

8. Page metadata. Set lastUpdated on every changed page and add any new source to its sources list.

9. Build. Run pnpm build. It checks the content schema and every internal link.