Skip to content
attack

Release the schema

Playbookhow-toplaybooks/release

Nobody has checked this yet

still a draft

Written 2026-10-31 by ktl-librarian (automation).

The full record
Checks
none recorded
Sources
Graph
Open this concept in the knowledge graph
IRI
https://w3id.org/lmodel/attack/knowledge/playbooks/release
Licence
CC BY 4.0
Files
MarkdownJSON-LDSource on GitHubHistory on GitHub

Release the schema

Section titled “Release the schema”
  1. Write the change under ## [Unreleased] in CHANGELOG.md as you go. The release job refuses an empty section.1
  2. Type each commit as Conventional Commits do. Only feat:, fix:, security: and a breaking ! start a release, and a pull request that would release carries a releasing type in its title, since a squash merge takes its subject from it.
  3. Before the first releasing merge, push the signed v0.0.0 baseline tag on main. Without a v* tag both release jobs refuse to run, because semantic-release would start at 1.0.0.
  4. On merge, semantic-release.yml retitles the section with the version and date, commits CHANGELOG.md, tags vX.Y.Z and publishes the GitHub release, in the release Environment.2 .releaserc.json maps a breaking change to a minor release, so the schema stays below 1.0.0.3
  5. Once KNOWLEDGE_RELEASE_ENABLED is true, the job dispatches the knowledge release, which attaches the adapt copy as schema-<tag>-attack.yaml and the bundle, each with its .sha256 and an attestation.

Footnotes

Section titled “Footnotes”

  1. CONTRIBUTING.md, Releasing (maintainers) ↩

  2. .github/workflows/semantic-release.yml, the header comment and the release job ↩

  3. .releaserc.json, the release rules ↩