v0.3.0 release cut#114
Merged
Merged
Conversation
Release-cut housekeeping for v0.3.0 — version bump + CHANGELOG aggregation, no behaviour change. - Bump the package version 0.2.0 -> 0.3.0 (pyproject.toml, __about__.py, CITATION.cff, uv.lock). DATASET_VERSION is already 0.3.0, so the Hub dataset/checkpoints and the leaderboard fixture stay in lockstep with the tag. - Bump the leaderboard Space's maneuver-detect pin to the v0.3 line (>=0.3.0,<0.4) so the hosted scorer installs the released package. - Aggregate the CHANGELOG [0.3.0] section: the Chronos forecast-residual foundation baseline, the IGSO class + QZSS/NOAA-GOES/Galileo operator label sources, uncertainty calibration (reliability/temperature/conformal + per-class operating points baked into the bundle), and the class-balanced selection objective + per-class thresholds. Ships the frozen v0.3 decisions D14-D17. Base runtime deps are unchanged and remain permissive; the [foundation] extra stays optional. Refresh the stale [foundation]-extra comment that still referenced the v0.1 surface. Closes #65
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
Release-cut housekeeping for v0.3.0 — version bump + CHANGELOG aggregation, no behaviour or dependency changes.
0.2.0→0.3.0(pyproject.toml,src/maneuver_detect/__about__.py,CITATION.cff,uv.lock).DATASET_VERSIONis already0.3.0, so the Hub dataset/checkpoints and the leaderboard fixture stay in lockstep with the tag.maneuver-detectpin to the v0.3 line (>=0.3.0,<0.4) so the hosted scorer installs the released package.CHANGELOG.md[0.3.0]section: the Chronos forecast-residual foundation baseline (optional[foundation]extra, zero-shot), the IGSO scored class + QZSS/NOAA-GOES/Galileo operator label sources (GEO now operator-announced, HEO reserved), uncertainty calibration (reliability/temperature/split-conformal + per-class operating points baked into the bundle, fit on val only), and the class-balanced selection objective + per-class detection thresholds. Ships the frozen v0.3 decisions D14–D17.[foundation]-extra comment that still claimed the extra was "not exercised by the v0.1 surface".Base runtime deps are unchanged and remain permissive (BSD/Apache/MIT); the
[foundation]extra (chronos-forecasting) stays optional. The model checkpoints (bilstm-base,transformer-base,chronos-residual) and dataset are published to the Hub in lockstep withv0.3.0.The
v0.3.0tag — PyPI trusted publish, Hub dataset/checkpoint publish, Pages redeploy, release-notes overwrite from the CHANGELOG, milestone close — follows once this merges.Test plan
ruff check,ruff format --check,mypycleanmkdocs build --strictbuilds[foundation]extra stays optionalCloses #65