Skip to content

Conversation

@kandersolar
Copy link
Member

  • Closes #xxxx
  • I am familiar with the contributing guidelines
  • Tests added
  • Updates entries in docs/sphinx/source/reference for API changes.
  • Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
  • New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
  • Pull request is nearly complete and ready for detailed review.
  • Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

Following the release procedure, this PR adds the whatsnew file template for the next version (v0.13.1).

@kandersolar kandersolar added this to the v0.13.1 milestone Jun 7, 2025
@kandersolar kandersolar merged commit a27c686 into pvlib:main Jun 7, 2025
25 of 26 checks passed
@kandersolar kandersolar deleted the next-whatsnew branch June 7, 2025 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

1 participant