Skip to content
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

Release v24.3.1 #369

Merged
merged 3 commits into from
Jun 18, 2024
Merged

Release v24.3.1 #369

merged 3 commits into from
Jun 18, 2024

Conversation

BradyPlanden
Copy link
Member

Description

Patch release for v24.3, upper pins Numpy to < 2.0.

Issue reference

Fixes #368

Review

Before you mark your PR as ready for review, please ensure that you've considered the following:

  • Updated the CHANGELOG.md in reverse chronological order (newest at the top) with a concise description of the changes, including the PR number.
  • Noted any breaking changes, including details on how it might impact existing functionality.

Type of change

  • New Feature: A non-breaking change that adds new functionality.
  • Optimization: A code change that improves performance.
  • Examples: A change to existing or additional examples.
  • Bug Fix: A non-breaking change that addresses an issue.
  • Documentation: Updates to documentation or new documentation for new features.
  • Refactoring: Non-functional changes that improve the codebase.
  • Style: Non-functional changes related to code style (formatting, naming, etc).
  • Testing: Additional tests to improve coverage or confirm functionality.
  • Other: (Insert description of change)

Key checklist:

  • No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
  • All unit tests pass: $ nox -s tests
  • The documentation builds: $ nox -s doctest

You can run integration tests, unit tests, and doctests together at once, using $ nox -s quick.

Further checks:

  • Code is well-commented, especially in complex or unclear areas.
  • Added tests that prove my fix is effective or that my feature works.
  • Checked that coverage remains or improves, and added tests if necessary to maintain or increase coverage.

Thank you for contributing to our project! Your efforts help us to deliver great software.

@BradyPlanden
Copy link
Member Author

BradyPlanden commented Jun 17, 2024

In it's current form, this PR is expected to fail due to tenacity's 8.4.0 release. I think this should be yanked or patched fairly quickly (see: jd/tenacity#474), so I am leaving the upper pin out of this PR/release.

Copy link

codecov bot commented Jun 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.33%. Comparing base (133af44) to head (820cb77).
Report is 1011 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #369   +/-   ##
=======================================
  Coverage   95.33%   95.33%           
=======================================
  Files          36       36           
  Lines        1971     1971           
=======================================
  Hits         1879     1879           
  Misses         92       92           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@agriyakhetarpal
Copy link
Member

tenacity v8.4.1 is out now. PyBaMM will soon provide the upper pin on NumPy v2, and I hope we'll remove it with either a patch v24.5.1 release or in the release candidate stage so that the stable version doesn't have it – we will most likely keep the pin in v24.5rc0. My only suggestion would be that if PyBOP does keep the upper pin here, it removes it in a further v24.3.2 and not with v24.5. :)

@BradyPlanden
Copy link
Member Author

BradyPlanden commented Jun 17, 2024

Thanks for the comment Argiya. We will need to upstream the fixes to Pints or integrate the failing code into PyBOP with fixes to remove the upper pin. I'm happy with either, but won't be able to take this on until the end of next week. Happy to have someone else take the lead otherwise.

The failed tests are expected, as Thevenin didn't have the standard vars we need in PyBaMM v23.5. This has been added in develop for the upcoming PyBOP v24.6.

@BradyPlanden
Copy link
Member Author

Just to add, I'm happy to have other fixes in this release if anyone has anything they would like included!

@agriyakhetarpal
Copy link
Member

Ah, I have been working on the docs, but I don't think I'll be able to make them ready in time – they would be better off in the v24.5 release.

Copy link
Member

@NicolaCourtier NicolaCourtier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks very much @BradyPlanden, looks good to me!

@BradyPlanden BradyPlanden merged commit 2a588e0 into main Jun 18, 2024
71 of 85 checks passed
@BradyPlanden BradyPlanden deleted the v24.3.1 branch June 18, 2024 11:28
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.

3 participants