Release rtichoke 0.1.29 - #294
Merged
Merged
Conversation
Contributor
|
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.
What changed
0.1.28to0.1.29pyproject.tomlchanges onmainv0.1.29) with generated release notes after a successful publishWhy
Ordinary package CI intentionally stopped publishing in #283. This restores publishing as an explicit release action tied to a reviewed version bump, so merges to
mainno longer try to republish an existing immutable PyPI version.Included work
This release includes the recently merged performance-data sorting, performance tables/Great Tables + Reactable renderers, calibration multi-population fix, integer time-horizon normalization, improved calibration heuristic validation, and the associated Great Docs documentation improvements.
Validation
The normal package and documentation PR workflows should run before merge. On merge, the new
Release packageworkflow will build and publish0.1.29, then create the GitHub release.