Skip to content

v0.2.2 — Zenodo archival, licence ID corrected

Choose a tag to compare

View all tags
@musharna musharna released this 31 Jul 04:52
v0.2.2
e94f48b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Archived to Zenodo. This release exists so the tag carries the citation metadata a DOI is minted from.

Why a release was required

The Zenodo↔GitHub integration mints its DOI from the tag's tarball. The previous tag predated .zenodo.json and CITATION.cff entirely — both were added after it was cut — so re-publishing the existing release could never have archived correct metadata, and Zenodo returns 409 on it regardless, having created a deposit on the first attempt that never became public.

Correction — these notes originally claimed a licence bug that does not exist

This release was first described as fixing a defect in which SPDX casing in .zenodo.json "silently dropped the licence from the published record". That was wrong, and the claim is retracted here rather than quietly removed.

Zenodo normalises the licence identifier on ingest. The sibling ldraw-mcp archived with "MIT" still in place and its record reads license: mit-license. Every record carries its licence correctly; the licence was never dropped.

The apparent evidence was two measurement errors, both the same mistake — probing a proxy instead of the artifact:

  1. Querying the licence vocabulary endpoint (MIT → 404, mit → 200) and treating that as what the ingest accepts. It is not.
  2. Reading the RDM-era field names (rights, subjects, creators[].person_or_org) against an API endpoint that returns the legacy shape (metadata.license, metadata.keywords, creators[].orcid). Every field reported as absent was present throughout.

The lowercase identifier is kept because it is the canonical spelling — it simply fixed nothing.

Verified before publishing

Version agreement across pyproject.toml, server.json (three fields) and CITATION.cff; cffconvert --validate against the CFF 1.2.0 schema; mcp-publisher validate; ruff check and format; registry metadata tests; twine check; the mcp-name marker confirmed inside the built wheel's METADATA; and both wheel and sdist confirmed present on the /simple/ index after upload.

No functional change — tools, guards and dependency pins are untouched.

Assets 2
Loading