Repository navigation
chore(release): v0.5.0 + automated tagging and GitHub Releases - #17
Merged
Merged
Conversation
…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>
8 tasks done
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.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.0package.json,package-lock.jsonandCITATION.cffare bumped 0.4.0 → 0.5.0 (date-released: 2026-10-15).CHANGELOG.md[0.5.0]section: 14 added records, 13 updated,openai-attributed-rubygems-agent-swarmmarked disputed, two confidence upgrades, ATLAS ids.dist/is rebuilt, so the published version stamp reads 0.5.0.maincurrently shows 0.4.0 for the 96-record data.ci(release).github/workflows/release.yml. When apackage.jsonchange reachesmain, it runsnpm test, reads the version, and does nothing ifv<version>already exists.dist/artifacts and the JSON Schema are attached.Additive minor bump: the schema is unchanged, so consumers need no migration.
v0.4.0has been tagged retroactively at its release commitf9de746, with a GitHub Release built from its changelog section.Checklist (Definition of done)
npm testpasses locally: 96 records (95 active), 16/16 tests;dist/rebuilt and committednpm run linkcheckresolved all 177 URLs.status/confidencehonestly reflect the sourcing (no data changes in this PR)mappingsIDs exist exactly as publishedidis new and permanent (no ids touched)CITATION.cffversion and date updatedRepo setting to check: the workflow uses the default
GITHUB_TOKENwithcontents: 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