Repository navigation
chore(release): v0.6.0 + flag unreleased changes on main - #19
Merged
Merged
Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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,
mainand 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.jsongains an additiveunreleased_changesboolean. It is true whenCHANGELOG.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.release.ymlrefuses to tag while[Unreleased]still has notes, so a release cannot ship with notes left behind.[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.hasUnreleasedChangeshas a unit test with four cases.chore(release): v0.6.0package.json,package-lock.jsonandCITATION.cff: 0.5.0 → 0.6.0 (2026-10-15).[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 testpasses locally (validate + build,dist/rebuilt and committed): 100 records, 17/17 testsstatus/confidencehonestly reflect the sourcing (no data changes)mappingsIDs exist exactly as publishedidis new and permanent (no ids touched)summary.jsongained one additive field, documented in the README and CHANGELOG.🤖 Generated with Claude Code