Skip to content

chore(release): v0.6.0 + flag unreleased changes on main - #19

Merged
RiccardoBiosas merged 2 commits into
mainfrom
release/v0.6.0
Oct 15, 2026
Merged

RiccardoBiosas merged 2 commits into
mainfrom
release/v0.6.0

Conversation

@RiccardoBiosas

Copy link
Copy Markdown
Contributor

What

Cuts dataset release v0.6.0 and fixes the problem that made it necessary: version-stamp drift between releases.

The problem. Data merged after a release kept the previous version number. After #18 merged, main and the Pages site showed "dataset 0.5.0" with 100 records, while the v0.5.0 GitHub Release holds 96. Consumers could not tell the two apart.

feat(summary)

  • dist/summary.json gains an additive unreleased_changes boolean. It is true when CHANGELOG.md's [Unreleased] section has content. It is derived from a file in the repo, so the build stays deterministic. Within the compatibility promise, since only a field is added.
  • The landing page shows "plus unreleased changes (see the CHANGELOG)" when the flag is true.
  • release.yml refuses to tag while [Unreleased] still has notes, so a release cannot ship with notes left behind.
  • CONTRIBUTING asks every data PR to add an [Unreleased] entry. data: intake sweep 2026-10-15 — 14 new incidents, 13 record updates #16 missed this, which is why its notes had to be backfilled in chore(release): v0.5.0 + automated tagging and GitHub Releases #17.
  • The README artifact table is updated, and hasUnreleasedChanges has a unit test with four cases.

chore(release): v0.6.0

  • package.json, package-lock.json and CITATION.cff: 0.5.0 → 0.6.0 (2026-10-15).
  • The data: triage Rogue Agents Watch brief — add 4 incidents #18 notes move into [0.6.0]: thailand-mof-hermes-agent-intrusion, blackhatsect0r-hermes-dxscan-harvesting, carbonato-docker-hermes-botnet, ai-augmented-fortigate-mass-compromise.
  • dist/ rebuilt: dataset_version: "0.6.0", unreleased_changes: false.

Merging this PR should tag v0.6.0 and publish its GitHub Release automatically, as happened for v0.5.0.

Checklist (Definition of done)

  • npm test passes locally (validate + build, dist/ rebuilt and committed): 100 records, 17/17 tests
  • Every changed record has ≥1 source with a working URL. No record data changed; data: triage Rogue Agents Watch brief — add 4 incidents #18's linkcheck resolved all 187 URLs.
  • status / confidence honestly reflect the sourcing (no data changes)
  • All enum values and mappings IDs exist exactly as published
  • id is new and permanent (no ids touched)
  • No exploit code, payloads, prompts, or step-by-step offensive detail
  • Victim orgs named only where a public/first-party disclosure already named them
  • Schema changed? No. summary.json gained one additive field, documented in the README and CHANGELOG.

🤖 Generated with Claude Code

RiccardoBiosas and others added 2 commits October 15, 2026 16:17
…e tagged release

Data merged between releases was stamped with the previous version: after
#18, main showed dataset 0.5.0 with 100 records while the v0.5.0 release
holds 96. summary.json gains an additive unreleased_changes boolean,
derived deterministically from a non-empty CHANGELOG [Unreleased] section,
and the landing page says so. The release workflow refuses to tag while
[Unreleased] has notes. CONTRIBUTING asks data PRs to add an [Unreleased]
entry. Unit-tested.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bumps package.json and CITATION.cff from 0.5.0 to 0.6.0 (2026-10-15) and
moves the #18 notes (4 incidents from the Rogue Agents Watch brief triage)
plus the unreleased_changes addition into [0.6.0]. An additive minor bump
with no schema change. npm test passes: 100 records, 17/17 tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RiccardoBiosas
RiccardoBiosas merged commit b59ec90 into main Oct 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant