Skip to content

Update changelog for 0.16 #720

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 7, 2025
Merged

Conversation

dstansby
Copy link
Contributor

@dstansby dstansby commented Apr 7, 2025

[Description of PR]

TODO:

  • Unit tests and/or doctests in docstrings
  • Tests pass locally
  • Docstrings and API docs for any new/modified user-facing classes and functions
  • Changes documented in docs/release.rst
  • Docs build locally
  • GitHub Actions CI passes
  • Test coverage to 100% (Codecov passes)

Copy link

codecov bot commented Apr 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.96%. Comparing base (b588f0f) to head (887c9e2).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #720   +/-   ##
=======================================
  Coverage   99.96%   99.96%           
=======================================
  Files          63       63           
  Lines        2738     2738           
=======================================
  Hits         2737     2737           
  Misses          1        1           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dstansby dstansby merged commit 197a03d into zarr-developers:main Apr 7, 2025
28 checks passed
@jakirkham
Copy link
Member

In the future, @dstansby, could you please start an issue planning for the release? That would allow us to organize any work that we would like to get in with an issue

@dstansby dstansby deleted the 016-clog branch April 7, 2025 20:29
@dstansby
Copy link
Contributor Author

dstansby commented Apr 7, 2025

👍 Sorry, happy to if it's helpful, but it would be good to list that as a requirement in the release procedure to make sure all developers are on the same page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants