Repository navigation
Record the 0.6.0 publication, add the Zenodo DOI, open 0.6.1.dev0 - #157
Merged
Merged
Conversation
- Release evidence: the publish run, guard, tests, approval, PyPI upload times, sizes and SHA-256, the fresh installation from PyPI, Read the Docs stable and the Zenodo archive. - CITATION.cff and the README carry the Zenodo concept DOI 10.5281/zenodo.23605678 and the 0.6.0 version DOI 10.5281/zenodo.23605679; the README has a DOI badge. - The 0.6.0 publishing checklist is complete, and the release history lists 0.6.0. - main opens 0.6.1.dev0 (pyproject, flahax.__version__, the manual title, the API reference); CITATION.cff stays at the released 0.6.0. Step 7 of the procedure. Closes #134
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #157 +/- ##
=======================================
Coverage 89.82% 89.82%
=======================================
Files 54 54
Lines 7371 7371
=======================================
Hits 6621 6621
Misses 750 750
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
rafatahmed
marked this pull request as ready for review
October 23, 2026 23:16
rafatahmed
added a commit
that referenced
this pull request
Nov 7, 2026
Record the 0.6.0 publication, add the Zenodo DOI, open 0.6.1.dev0
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
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.
The steps after publishing 0.6.0, from the release procedure.
0.6.0 is published
v0.6.0on03e03ef, the merge of Finalize 0.6.0: date the release 2026-10-24 #156.pypideployment.06954424…), sdist 5,437,125 bytes (8453b700…);flahax --versionprints 0.6.0, with 135 public names;flahax batchwrites all three files;flahax mix --helplists--plain.stableserves the restructured site, and the old addresses redirect.What changes
docs/site/evidence/release-evidence.mdgains the 0.6.0 publication record, with the run, upload times, sizes, hashes, the fresh install, the docs and the archive.CITATION.cffgetsdoi:(concept) andidentifiers(concept and 0.6.0);preferred-citationgets the 0.6.0 DOI;docs/publishing.md: the 0.6.0 checklist is complete, and the release history lists 0.6.0.maininpyproject.toml,flahax.__version__, the manual title and the API reference.CITATION.cffstays at the released 0.6.0. A development version sorts after 0.6.0, so installing from GitHub replaces the release (main carries the released version 0.5.0, so pip install --upgrade from GitHub keeps the old package #99); the README already explains--force-reinstallbetween development commits.Checks
CITATION.cffparses as YAML.tools/verify_distribution.pypasses, and the strict Sphinx build passes.Closes #134