Skip to content

chore(release): v0.5.0 + automated tagging and GitHub Releases - #17

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

RiccardoBiosas merged 2 commits into
mainfrom
release/v0.5.0

Conversation

@RiccardoBiosas

Copy link
Copy Markdown
Contributor

What

Cuts dataset release v0.5.0 for the 2026-10-15 intake sweep (#16). It also fixes two release-process gaps: the changelog had no entry for #16, and no release had ever been tagged.

  • chore(release): v0.5.0
    • package.json, package-lock.json and CITATION.cff are bumped 0.4.0 → 0.5.0 (date-released: 2026-10-15).
    • New CHANGELOG.md [0.5.0] section: 14 added records, 13 updated, openai-attributed-rubygems-agent-swarm marked disputed, two confidence upgrades, ATLAS ids.
    • dist/ is rebuilt, so the published version stamp reads 0.5.0. main currently shows 0.4.0 for the 96-record data.
  • ci(release)
    • New .github/workflows/release.yml. When a package.json change reaches main, it runs npm test, reads the version, and does nothing if v<version> already exists.
    • Otherwise it creates the tag and a GitHub Release. The notes are that version's CHANGELOG section, and the job fails if the section is missing. The dist/ artifacts and the JSON Schema are attached.
    • CONTRIBUTING gains a Releasing section.
    • Merging this PR should therefore tag v0.5.0 automatically.

Additive minor bump: the schema is unchanged, so consumers need no migration.

v0.4.0 has been tagged retroactively at its release commit f9de746, with a GitHub Release built from its changelog section.

Checklist (Definition of done)

  • npm test passes locally: 96 records (95 active), 16/16 tests; dist/ rebuilt and committed
  • Every changed record has ≥1 source with a working URL. Record data is unchanged since data: intake sweep 2026-10-15 — 14 new incidents, 13 record updates #16, where npm run linkcheck resolved all 177 URLs.
  • status / confidence honestly reflect the sourcing (no data changes in this PR)
  • 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; CITATION.cff version and date updated

Repo setting to check: the workflow uses the default GITHUB_TOKEN with contents: write. If Settings → Actions → Workflow permissions is set to read-only and that ceiling blocks the job-level grant, the job will fail at the release step. If so, switch that setting to read and write.

🤖 Generated with Claude Code

RiccardoBiosas and others added 2 commits October 15, 2026 15:26
…ches main

No release had ever been tagged, so consumers could not pin a dataset
version. The workflow reads package.json, skips if v<version> already
exists, extracts that version's CHANGELOG section as notes (failing if it
is missing) and attaches the dist/ artifacts and the JSON Schema.
CONTRIBUTING gains a Releasing section.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bumps package.json and CITATION.cff from 0.4.0 to 0.5.0 (date-released
2026-10-15) and adds the missing CHANGELOG section for the 2026-10-15 intake
sweep (#16: 14 new records, 13 updated, RubyGems record disputed). Rebuilds
dist/ so the version stamp reads 0.5.0. This is an additive minor bump with
no schema change. npm test passes: 96 records (95 active), 16/16 tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RiccardoBiosas
RiccardoBiosas merged commit e0803ea 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