Restore the v1.1.0 slot to its deposited artifacts, and prepare the v1.2.0 deposit - #101
Merged
Merged
Conversation
…1.2.0 deposit Closes the open item recorded with v1.2.0: the repository's tracked v1.1.0 PDF was not the artifact the v1.1.0 DOI resolved to. WHAT WAS WRONG. The DOI was assigned AFTER the artifact was frozen, so the deposited PDF says the DOI was not yet assigned. The natural repair -- regenerate the PDF with the DOI in it -- was applied to the version slot that must not change. A reader of the repository's v1.1.0 PDF was therefore not reading what the v1.1.0 DOI resolves to. WHAT WAS DONE. Both v1.1.0 artifacts restored to their published state: the manuscript from tag paper-v1.1.0, the PDF downloaded from the Zenodo deposit. The DOI-bearing text now lives where it belongs, in v1.2.0. VERIFIED, NOT ASSERTED. Building the restored manuscript on this machine reproduces the deposited PDF BYTE-FOR-BYTE, sha256 10413b41... That single check establishes three things: the restoration is correct; the ReportLab build is deterministic across machines; and the version-derived build change introduced with v1.2.0 does not disturb v1.1.0's reproduction. A hardcoded version string would have produced a different PDF and this check would have failed, so the change made for tidiness turns out to be load-bearing. PREPARED FOR THE NEXT DEPOSIT. .zenodo.json now describes v1.2.0, dated 2026-08-18, and declares isNewVersionOf 10.5281/zenodo.21965713 so Zenodo links the version family. It is the input to a deposit, not a deposit. STILL NOT DONE, AND NOT BY AN AGENT: no tag, no release, no Zenodo publication, no arXiv submission. A DOI is immutable once published and the repository's own checklist requires the draft deposit to be inspected and approved first. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Closes the open item recorded with v1.2.0.
What was wrong
The DOI was assigned after the artifact was frozen, so the deposited PDF says "DOI: not yet assigned". The natural repair — regenerate the PDF with the DOI in it — was applied to the one version slot that must not change.
What was done
Both v1.1.0 artifacts restored to their published state — manuscript from tag
paper-v1.1.0, PDF downloaded from the Zenodo deposit. The DOI-bearing text now lives where it belongs, in v1.2.0.Verified, not asserted
That third line is the one that matters. It establishes three things at once:
A hardcoded version string would have stamped
v1.2.0into this rebuild and the hashes would not have matched. The change made for tidiness turns out to be load-bearing, and this is the check that proves it.Prepared for the next deposit
.zenodo.jsonnow describes v1.2.0, dated 2026-08-18, and declaresisNewVersionOf 10.5281/zenodo.21965713so Zenodo links the version family. It is the input to a deposit, not a deposit.Still not done, and not by an agent
No tag. No release. No Zenodo publication. No arXiv submission.
A DOI is immutable once published, and your own checklist requires the draft deposit to be inspected and approved before publishing. After this merges I can cut the
paper-v1.2.0tag and GitHub release on request — the Zenodo draft then appears for you to inspect and publish.paper-checkpasses; 426 passed, 8 skipped; integrity checks green.🤖 Generated with Claude Code