diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 388d3f2..1ca1480 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -39,6 +39,14 @@ jobs: echo "skip=true" >> "$GITHUB_OUTPUT" fi + - name: Require an empty [Unreleased] section + if: steps.exists.outputs.skip != 'true' + run: | + if [ "$(node -p "require('./dist/summary.json').unreleased_changes")" = "true" ]; then + echo "::error::CHANGELOG [Unreleased] still has notes; move them into the version section before releasing." + exit 1 + fi + - name: Extract release notes from CHANGELOG if: steps.exists.outputs.skip != 'true' run: | diff --git a/CHANGELOG.md b/CHANGELOG.md index 7093f37..fc3c6db 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,18 @@ dataset version tracks `package.json` and `CITATION.cff` (kept in sync by ## [Unreleased] +## [0.6.0] - 2026-10-15 + +### Added +- `dist/summary.json` gained **`unreleased_changes`** (boolean). It is true + when `CHANGELOG.md`'s `[Unreleased]` section has content, meaning `main` + carries changes that no tagged release contains yet. The landing page shows + "plus unreleased changes" in that case. Before this, data merged between + releases appeared under the previous version number: after #18 the site + showed "0.5.0" for 100 records, while the v0.5.0 release holds 96. +- The release workflow refuses to tag while `[Unreleased]` still has notes. + CONTRIBUTING now asks every data PR to add an `[Unreleased]` entry. + ### Data - Triage of an external candidate brief (Rogue Agents Watch, 2026-10-15). Of the candidates not already in the catalog, four passed re-validation against diff --git a/CITATION.cff b/CITATION.cff index 02a9829..8eac63d 100644 --- a/CITATION.cff +++ b/CITATION.cff @@ -10,7 +10,7 @@ authors: website: "https://mlsecopshub.com" repository-code: "https://github.com/MLSecOpsHub/agentic-attack-index" url: "https://mlsecopshub.com" -version: 0.5.0 +version: 0.6.0 date-released: 2026-10-15 license: CC-BY-SA-4.0 keywords: diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 857d2f5..d4364b3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -49,6 +49,7 @@ Update the fields, add the new source(s), bump `last_updated`, and keep the `id` ## Commits and PRs - Conventional Commits; data changes use the `data:` scope (e.g. `data: add `). +- Every data PR adds a line under `## [Unreleased]` in `CHANGELOG.md`. That section drives `unreleased_changes` in `dist/summary.json`, so consumers can see when `main` is ahead of the latest tagged release. - CI runs `npm test`; nothing merges red. - Trust-critical paths (`data/`, `schema/`, `taxonomy/`, `scripts/`, `.github/`) have code owners (`.github/CODEOWNERS`). For this to actually gate merges, enable branch protection on `main` with **Require a pull request before merging**, **Require review from Code Owners**, and **Require status checks to pass** (select the `validate + build` check) — these are GitHub repo settings, not files in the repo. - If you change `schema/`, update `README.md`, the taxonomy files, and `CITATION.cff` as needed, and explain the migration in the PR. @@ -58,7 +59,7 @@ Update the fields, add the new source(s), bump `last_updated`, and keep the `id` The dataset follows semantic versioning: added records or enum values are a minor bump; a removed or renamed field or enum value is a major bump with a migration note. To cut a release: 1. On a `release/vX.Y.Z` branch, set the same version in `package.json` (`npm version X.Y.Z --no-git-tag-version`, which also updates `package-lock.json`) and in `CITATION.cff`, along with `date-released`. -2. Move the `[Unreleased]` notes in `CHANGELOG.md` into a dated `[X.Y.Z]` section. +2. Move the `[Unreleased]` notes in `CHANGELOG.md` into a dated `[X.Y.Z]` section, leaving `[Unreleased]` empty. The release workflow refuses to tag otherwise. 3. Run `npm test` and `npm run linkcheck`, commit the rebuilt `dist/` as `chore(release): vX.Y.Z`, and open a PR. 4. After the merge, `.github/workflows/release.yml` creates the `vX.Y.Z` tag and a GitHub Release. The release notes come from the changelog section, and the `dist/` artifacts and schema are attached. The workflow fails if that section is missing. diff --git a/README.md b/README.md index f7572e7..5bdae59 100644 --- a/README.md +++ b/README.md @@ -38,7 +38,7 @@ npm run build # writes the dist/ artifacts below | `dist/incidents.ndjson` | newline-delimited JSON (streaming) | | `dist/incidents.csv` | flattened columns for spreadsheets (map points as `geo_points` = `role:basis:country`) | | `dist/incidents/.json` | one file per incident (stable per-record URL) | -| `dist/summary.json` | counts + rollups (category, severity, status, actor type, autonomy level, AI role, model family, year) + `archive_coverage` + `geo_coverage` (points by role and basis) + `evidence_split` (records that are both `confirmed` and `load-bearing`, overall and by year, plus a status × AI-role crosstab; retracted/superseded excluded) | +| `dist/summary.json` | `dataset_version` + `unreleased_changes` (true when `main` is ahead of that tagged release) + counts + rollups (category, severity, status, actor type, autonomy level, AI role, model family, year) + `archive_coverage` + `geo_coverage` (points by role and basis) + `evidence_split` (records that are both `confirmed` and `load-bearing`, overall and by year, plus a status × AI-role crosstab; retracted/superseded excluded) | | `dist/stix/bundle.json` | STIX 2.1 bundle (reports + ATLAS/ATT&CK attack-patterns + CVE vulnerabilities) for TIP/MISP ingestion | | `dist/index.html` | landing page (served via GitHub Pages) | diff --git a/dist/index.html b/dist/index.html index c25b8e2..3d197a9 100644 --- a/dist/index.html +++ b/dist/index.html @@ -3,7 +3,7 @@ -Agentic Attack Index — dataset 0.5.0 +Agentic Attack Index — dataset 0.6.0