Release notes for v0.21, to support latest ecCodes. #597
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## v0.21.x #597 +/- ##
===========================================
+ Coverage 89.60% 89.81% +0.21%
===========================================
Files 8 8
Lines 2473 2475 +2
Branches 420 406 -14
===========================================
+ Hits 2216 2223 +7
+ Misses 159 155 -4
+ Partials 98 97 -1 ☔ View full report in Codecov by Sentry. |
pp-mo
force-pushed
the
whatsnew_0v21
branch
2 times, most recently
from
f28f7f1 to
808a3e5
Compare
ESadek-MO
approved these changes
Jan 7, 2025
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.
This wraps up all the latest changes into a v0.21.0 release.
In the usual way, we'll create a separate branch for this in case we need to make a bugfix release, though we're unlikely to use it.
The whatsnew changes will afterwards be merged back to the main, at which point we'll readjust the main index page to read "v0.22 (unreleased)", just to avoid confusion. But probably no other changes will occur at that point.