release: GLIDER 1.0.0 - #112
Merged
Merged
Conversation
Version 0.3.0-dev -> 1.0.0, and the changelog consolidated into a single 1.0.0 entry. It had drifted into three sections describing one unreleased state: a [1.1.0] block, an [Unreleased] release-prep block, and a [1.0.0] "planned" block still dated 2026-XX-XX. Nothing was dropped -- the feature list, the release-prep work, and the fixes are merged under one heading with the known limitations kept. Adds CITATION.cff, which the changelog has claimed since the release-prep work but which was never actually written, and .zenodo.json so a DOI minted from the GitHub release carries correct metadata rather than the repository defaults. The manuscript's behavior-classification results were produced at d4e4b43, an ancestor of this commit, so citing 1.0.0 for those numbers is accurate.
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.
Prepares the first public release, citable from the paper.
Version
0.3.0-dev→ 1.0.0, consistent across_version.py(the single sourcepyproject.tomlreads dynamically),CITATION.cff,.zenodo.jsonand thechangelog heading.
Changelog consolidation
It had drifted into three sections describing one unreleased state:
[1.1.0] — 2026-07-11(live classifier, onboarding tour, GPU diagnostics, macOS packaging)[Unreleased] — release-prep-1.0 branch(the engineering audit work)[1.0.0] — 2026-XX-XX (planned)(the feature list)None of it had shipped. Merged into a single
[1.0.0] — 2026-08-07entry —Major features / Added / Changed / Fixed / Removed / Known limitations — with
every bullet preserved verbatim.
Citation
CITATION.cff— the changelog has listed this since the release-prepwork but the file was never written. Now it exists, so GitHub's "Cite this
repository" button works.
.zenodo.json— so a DOI minted from the release carries propermetadata instead of repository defaults.
Provenance check
final_benchmark.jsonrecords the manuscript's behaviour-classificationresults at commit
d4e4b43. That commit is an ancestor of this branch, sociting v1.0.0 for those numbers is accurate rather than approximate.
Verification
2882 passed, 1 skipped; ruff and black clean;test_cli_versionandtest_updaterpass against the new version.Two things needing a human
A stray local tag.
v1.1.0exists locally, points at4f357ffwhich isnot on main, and was never pushed. It predates the 1.1.0 changelog entry it
appears to belong to. Recommend
git tag -d v1.1.0before tagging 1.0.0 —otherwise a later real 1.1.0 collides with it.
Zenodo must be enabled before tagging. The DOI is minted by a webhook when
the GitHub release is published; turning it on afterwards does not
retroactively mint one for that release. Enable the repo at zenodo.org first,
then tag.