Release 2.2.0 - #69
Merged
Merged
Conversation
Minor rather than patch: no trait, allowable value, unit or APD identifier moved, and nothing built against 2.1.2 becomes invalid -- but two things consumers parse did change. Dates are YYYY-MM-DD where they were D/M/YYYY, so code that split on "/" or parsed day-first needs updating; and 1,371 literals that were typed with a prefixed name now carry an absolute XMLSchema# datatype URI. Closes every entry on the known-gaps register -- the first time it has been empty since it was introduced. export/ is unchanged: #68 already committed the rebuilt artefacts, and this release snapshots them rather than regenerating them differently. release/2.2.0/ carries 10 files rather than the usual 9, the extra being LICENSE. COMMITMENTS.md had three references that the emptied register made stale: C3 deferred datatype problems to "gap C5", C5 pointed at a gap below that no longer exists, and the register preamble described debt that is now cleared. C9 goes from two unarchived releases to three -- Zenodo is a manual upload and 2.1.1 and 2.1.2 were already outstanding. Refs #59 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Member
Author
|
@ehwenk Can I leave you to complete this and post the new release as instructed? No rush, whenever you have time |
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
2 participants
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.
Cuts 2.2.0, which publishes the work from #68 (all seven known gaps closed).
Why minor, not patch
No trait, allowable value, unit or APD identifier changed, and nothing built against 2.1.2 becomes invalid. But two things consumers parse did change, which is more than a patch should carry:
YYYY-MM-DDwhere they wereD/M/YYYY. Code that splitdcterms:createdon/, or parsed it day-first, needs updating.Two published URIs also changed, though neither is APD-minted and neither was correct before: the Cerrado Recruitment term had a stray slash and resolved to nothing, and an orphan NCI Thesaurus URI that nothing referenced was removed.
What's in the snapshot
release/2.2.0/carries 10 files rather than the usual 9 — the extra isLICENSE. Until now the four released CSVs stated no licence andrelease/<version>/LICENSEwas a 404, so anyone downloadingAPD_traits.csvhad nowhere to read the terms.Verified: version consistent in
index.html, dates ISO 8601 in the RDF,LICENSEnaming CC BY 4.0 beside the data,make checkgreen with 1,586 tests and no known gaps.export/is unchanged — #68 committed the rebuilt artefacts and this snapshots them.Documentation
The emptied register left three stale references in
COMMITMENTS.md, now fixed: C3 deferred datatype problems to "gap C5", C5 pointed at a gap below that no longer exists, and the register preamble described debt that is cleared. C9 moves from two unarchived releases to three.After merging — the manual steps
Per
RELEASING.md, and in this order:git checkout develop && git pullbefore anything else —git merge --ff-only developmerges your local ref, and skipping the pull silently publishes the commit before the release.master, tagv2.2.0, create the GitHub Release with therelease/2.2.0/files as assets.apd_versionto"2.2.0"inaustraits.build/scripts/build_traits_yml_from_APD.R— it reads the release over HTTP, so this cannot run until the deploy lands.Refs #59
🤖 Generated with Claude Code