Repository navigation
Post-v1.3.0 housekeeping: concept DOI fix, PyPI badge, checklist update - #103
Merged
Merged
Conversation
10.5281/zenodo.21097248 is the v1.0.0 version DOI, so the README badge and citation metadata sent readers to the v1.0.0 record permanently. The concept DOI is 10.5281/zenodo.21097247 — verified to resolve to the latest archived release (currently v1.3.0, 10.5281/zenodo.21276606) — which is what both files always claimed to carry. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
quantscenariobench 1.3.0 is live on PyPI (wheel + sdist, verified by a clean-venv install and smoke test). Adds the PyPI version badge to the README, removes the release checklist's "not on PyPI" warning (and notes the ==X.Y.Z pin option for the Space), and updates the v1.3.0 CHANGELOG note written before the upload happened. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
q_a/ holds local Q&A working files (never team-shared; q_a/1 and q_a/2 have always been untracked). Ignoring it keeps session scratch out of git status. Intentionally leaves _bmad-output/, specs/, and benchmark_playground.py untracked-but-visible — those are handled together in the planned BMAD cleanup PR. Co-Authored-By: Claude Fable 5 <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.
Summary
Post-release cleanup after v1.3.0 shipped to PyPI, plus one real bug found while verifying the release:
98268b8) — the README badge andCITATION.cffcarried10.5281/zenodo.21097248, which is the v1.0.0 version DOI, so both permanently pointed at the v1.0.0 record. The actual concept DOI is10.5281/zenodo.21097247— verified to resolve to the latest archive (currently the v1.3.0 record,10.5281/zenodo.21276606). Zenodo did archive every release (v1.0.0–v1.3.0); only the reference was wrong.b6eb282) — PyPI version badge in the README, the release checklist's "not on PyPI" warning removed (and the==X.Y.ZSpace-pin option noted), and the v1.3.0 CHANGELOG note (written pre-upload) updated to state the publication happened.Release verification performed
quantscenariobench 1.3.0live with wheel + sdist; clean-venvpip install quantscenariobench==1.3.0imports from site-packages and passes asimulate()→realism_report()andrun_benchmark(HierarchicalRiskParity())smoke test.v1.3.0on the merge commit, Release published.10.5281/zenodo.21276606under concept10.5281/zenodo.21097247.🤖 Generated with Claude Code