Skip to content

Record the v0.2.0 release #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
doytsujin merged 1 commit into from
Sep 28, 2026
Merged

Record the v0.2.0 release #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -419,10 +419,18 @@ history — not as a consequence of this release.
release. Worth knowing before the next one — the URL set is not something
that can be tidied later in place.

- [ ] **`v0.2.0` — prepared 2026-09-27.** Two vectors for checks no vector reached before: `ad-003-stale-grant-executes-nothing` and `ad-004-clearance-refusal-has-no-grant` (F-012), with the mutants `StaleGrantsAccepted` and `ClearanceIgnored` that only they catch. The suite goes from 15 to 17 vectors and from 84 to 90 steps; the matrix is 19/19. **A minor bump, not a patch:** an implementation that passed `0.1.0` can fail `0.2.0`, which is the point of the two vectors. Both distributions move to `0.2.0` together, as a pair, though `authorized-recall` has no code change; the root distribution's lower bounds follow.
- [x] **`v0.2.0` — prepared 2026-09-27, released 2026-09-28.** Two vectors for checks no vector reached before: `ad-003-stale-grant-executes-nothing` and `ad-004-clearance-refusal-has-no-grant` (F-012), with the mutants `StaleGrantsAccepted` and `ClearanceIgnored` that only they catch. The suite goes from 15 to 17 vectors and from 84 to 90 steps; the matrix is 19/19. **A minor bump, not a patch:** an implementation that passed `0.1.0` can fail `0.2.0`, which is the point of the two vectors. Both distributions move to `0.2.0` together, as a pair, though `authorized-recall` has no code change; the root distribution's lower bounds follow.

**The DOI was reserved before the tag, as the `v0.1.0` entry above asked.** New-version draft 23005806 under concept 22536342; version DOI `10.5281/zenodo.23005806`, written into `CITATION.cff`, the README and the citation page before tagging, so this archive can cite itself.

Also in this release: the README's *release candidate* status block, stale since `v0.1.0` was tagged on 2026-09-06, is replaced; the docs generator no longer emits links to GitHub paths that do not exist (eight on the live site did); the MCP server reports the library's version instead of a literal `0.1.0`. EMBC 2026 re-checked against Crossref: still not in proceedings.

Remaining, in order: build and `twine check`; read the rendered description; clean-room install of both wheels; push; tag `v0.2.0`; upload to PyPI; archive the tag's `git archive` on the draft; verify Rights and version on the rendered draft; publish.
**Released 2026-09-28**, in the order above. Tagged `v0.2.0` on the merge commit d4bca1e, whose tree is identical to the release commit that was tested. Both distributions were built from the tag's exported tree, not the working copy, and match the tested build file for file; `twine check --strict` passes on all four. <https://pypi.org/project/agentic-dataset-conformance/0.2.0/> and <https://pypi.org/project/authorized-recall/0.2.0/>. A plain `pip install` in a fresh venv resolved `0.2.0` on the first try and runs 17 vectors, 90 steps, 15/15; no index lag this time.

**Zenodo record 23005806 published**, version DOI [10.5281/zenodo.23005806](https://doi.org/10.5281/zenodo.23005806). The archive is `git archive --format=zip --prefix=agentic-datasets-reference-0.2.0/ v0.2.0` (334,262 bytes, md5 `34400273567b6164e8978b10ffc80b55`) — the method of `v0.1.0`, confirmed by rebuilding that archive from its tag and matching Zenodo's checksum. The archive's `CITATION.cff` carries its own version DOI, which is what reserving first was for.

**The draft could not be read as rendered.** Its preview page answers 404 to an API token, since the web UI needs a session. What was read instead is the stored draft — the check that exposed the `v0.1.0` licence loss, as distinct from the payload sent — showing all four rights resolved to their titles, version `0.2.0`, one file, no validation errors. The rendered check was then made on the published landing page, anonymously: all four licences, version 0.2.0. The concept DOI resolved to the new record at once; the version DOI 404'd at `doi.org` for about a minute until DataCite registered it (04:18:28 UTC, 65 s after publish). A 404 right after publishing is registration lag, not a failure.

**Dates.** `CITATION.cff` `date-released` and the record's `publication_date` say 2026-09-27, the day the release commit was made; the merge, tag and publish fell just after midnight, on 2026-09-28. Left as it is: the archived file and the record agree, and changing either now would cost another version.

`make deploy` run after publishing: agenticdatasets.org and the Pages mirror both carry the `v0.2.0` citation and status, and every GitHub link on the changed pages answers 200.
Loading