Release v3.2.0 - #28
Merged
Merged
Conversation
2.1.3 is a records-only release: it names the countersigning human reviewer and changes no term, shape, fixture or expected answer. The bundle differs from the vendored 2.1.2 copy only in its owl:versionIRI and owl:versionInfo stamps, and every SHACL file is byte-identical to the checkout. Shipping 2.1.2 in v3.2.0 would make test_the_vendored_copies_match_the_ vocabulary_checkout fail on any machine with a current vocabulary checkout, and would cite a superseded vocabulary release. The provenance now records the v2.1.3 tag's commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
#26 added vcf-rdfizer-policy and docs/policy-demonstrator.md, but the README still listed only the privacy design proposal. It now names the fifth capability, gives the evaluate/check commands in a short subsection beside the linking plug-ins, and lists the policy modules and bundled data in the repository layout and the docs table. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A minor: two new host-side capabilities and a regional-access investigation, none of which changes what a v3.1.0 conversion writes. - vcf-rdfizer-policy (#26): ODRL policies attached to files, regions and variants, one release view per request, and checks that each view withholds exactly what the policy says, against the source graph and optionally the VCF text. Selectors and ownership are declared in Turtle. - Multiple COTTAS index orders and N-Quads datasets (#24): any of the six triple orders or 24 graph-aware orders, each with its own bounded merge and round-trip check. - --validation-queries (#25): a run can answer a subset of the suite. A subset reports TIMING_ONLY rather than a verdict, and every selected query is still compared against the VCF oracle. - An indexed regional-access runner (#23): region-restricted questions asked of tabix/bcftools and of every SPARQL engine. The image gains tabix/bgzip. - Fixes: the missing-token check no longer reports a header's own Number=. (#22); a non-UTF-8 input fails at input-encoding instead of crashing the expanded run, and macOS ._* sidecars are skipped (#27). - VCF Core 2.1.3 vendored (records-only relabel of 2.1.2). Conda sha256 returns to its placeholder until the tag exists; populate it with `python3 scripts/release.py 3.2.0 --fetch-conda-sha256` after pushing v3.2.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Bumps the release metadata to 3.2.0 with
python3 scripts/release.py 3.2.0, followingscripts/RELEASING.mdand the v3.1.0 pattern (#19, then #20 for the conda checksum).Commits
owl:versionIRIandowl:versionInfostamps, and every SHACL file is byte-identical. Without this,test_the_vendored_copies_match_the_vocabulary_checkoutfails on any machine with a current vocabulary checkout, and the release would ship a superseded vocabulary.vcf-rdfizer-policy, but the README still listed only the design proposal. This adds a short subsection beside the linking plug-ins, plus rows in the repository layout and docs tables.pyproject.toml,CITATION.cff,README.mdandconda-recipe/. The conda sha256 returns to its placeholder until the tag exists.What v3.2.0 ships (since v3.1.0)
vcf-rdfizer-policy: ODRL policy attachment, per-request release views, and checks, including one against the VCF text--validation-queries, which selects a subset of the suite (TIMING_ONLY, still oracle-checked)tabix/bgzipNumber=.._*sidecars are skippedVerified
python3 scripts/release.py --check-tag v3.2.0reports: release metadata matches.vcf_rdfizer_data/policy/*.ttlfiles are packaged.vcf-rdfizer-policy evaluatereproduces the documented result: 76 records released, 4,649 triples withheld.check --vcfpasses.After merge
git tag -a v3.2.0 -m "VCF-RDFizer v3.2.0"on the merge commit, then push the tag. This runs publish-python (PyPI) and publish-docker (3.2.0,v3.2.0,latest; amd64 and arm64).python3 scripts/release.py 3.2.0 --fetch-conda-sha256and a follow-up PR.conda-forge/vcf-rdfizer-feedstock.🤖 Generated with Claude Code