[Release]: 2026.08.28

[eddie-knight]

Version

2026.08.28

Release checklist

• Ensure all pull requests targeted for this release are merged
• Generate a static version of the baseline: cd cmd && go run . compile --output ../docs/versions/2026-08-28.md --checklist-output ../docs/versions/2026-08-28-checklist.md --crosswalk-output ../docs/versions/2026-08-28-crosswalk.md --artifact-version v2026.08.28
• In the docs/versions/<PREVIOUS_VERSION>.md file, remove the nav-title header block
• In the docs/versions/<VERSION>.md file, change the Version: devel to have the version number of the new version
• In the docs/versions/<VERSION>.md file, remove the "not for production use" warning
• In the docs/versions/<VERSION>.md file, add the nav-title
• In the docs/_config.yml file, update the listing in the nav_pages group to point to the new release
• In the docs/versions/<VERSION>-checklist.md and docs/versions/<VERSION>-crosswalk.md files, change the headers to have the version number of the new version
• Move the link to the "current" version in docs/index.md to the "previous versions" list
• Add the link to the new version to the "current version" in docs/index.md
• Make sure the docs/versions/release_notes.md file contains an accurate list of changes and is not commented out
• Open a pull request with the above changes (Release version 2026.08.28 of the Baseline #542)
• After the pull request is merged, git tag the commit
• Publish a GitHub Release from that tag — this is what triggers the grc.store publish workflow; a bare git tag will not fire it
• After the pull request is merged, send an email to the mailing list
• After the pull request is merged, notify OpenSSF's marketing team that we have a new release so that they can share it with the world