Release v1.60.0

[blooop]

Release v1.60.0

This release updates numpy to the latest version and includes important dependency updates.

Changelog

Changed

• Updated numpy version constraint from <=2.2.6 to <=2.4.1 to support latest numpy releases
• Updated all dependencies to latest compatible versions through pixi update

Fixed

• Resolved historical hvplot compatibility issues with numpy 2.x that were preventing updates

What's Included

• NumPy updated to 2.4.1 (from 2.2.6)
• All dependencies updated to latest compatible versions
• Full test suite passes with 89% coverage

Auto-Release

This PR will trigger the auto-release workflow upon merge to publish version 1.60.0 to PyPI.

🤖 Generated with Claude Code

Summary by Sourcery

Prepare the 1.60.0 release by updating the project version and documenting the updated dependency constraints and compatibility fixes.

Bug Fixes:

• Document resolution of historical hvplot compatibility issues with NumPy 2.x that previously blocked dependency updates.

Enhancements:

• Document updated NumPy version constraints and refreshed dependencies aligned with the current ecosystem in the changelog.

Chores:

• Bump the package version from 1.59.0 to 1.60.0 for the 1.60.0 release.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Release v1.60.0 bumps the library version, updates the changelog for the new release, and documents the numpy/dependency updates and resolved hvplot compatibility issues.

File-Level Changes

Change	Details	Files
Document v1.60.0 release details and dependency updates in the changelog.	Add 1.60.0 section with Changed/Fixed notes describing numpy constraint bump and pixi-driven dependency updates Document technical background on previous numpy 2.x and hvplot compatibility issues and their resolution Record that the full test suite passes with updated dependencies	CHANGELOG.md
Bump package version for the new release.	Increment project version from 1.59.0 to 1.60.0 in project metadata	pyproject.toml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `CHANGELOG.md:8-20` </location>
<code_context>
+## [1.60.0] - 2026-01-24
+
+### Changed
+- Updated numpy version constraint from `<=2.2.6` to `<=2.4.1` to support latest numpy releases
+- Updated all dependencies to latest compatible versions through pixi update
+
+### Fixed
+- Resolved historical hvplot compatibility issues with numpy 2.x that were preventing updates
+
+### Technical Details
</code_context>

<issue_to_address>
**suggestion (typo):** Consider using the standard "NumPy" capitalization for the library name, if that matches the rest of the project.

Here, "numpy" appears multiple times; the official spelling is "NumPy". Please align with the rest of the project’s docs/conventions, or ignore if you intentionally standardize on lowercase.

```suggestion
## [1.60.0] - 2026-01-24

### Changed
- Updated NumPy version constraint from `<=2.2.6` to `<=2.4.1` to support latest NumPy releases
- Updated all dependencies to latest compatible versions through pixi update

### Fixed
- Resolved historical hvplot compatibility issues with NumPy 2.x that were preventing updates

### Technical Details
- The NumPy version limitation was due to binary compatibility issues between NumPy 2.0 and hvplot that occurred when NumPy 2.0 was released in June 2024
- These issues have been fully resolved in the ecosystem, with hvplot 0.12.2 now fully compatible with NumPy 2.4.x
- All tests pass successfully with the updated dependencies
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

suggestion (typo): Consider using the standard "NumPy" capitalization for the library name, if that matches the rest of the project.

Here, "numpy" appears multiple times; the official spelling is "NumPy". Please align with the rest of the project’s docs/conventions, or ignore if you intentionally standardize on lowercase.

Suggested change

	## [1.60.0] - 2026-01-24
	### Changed
	- Updated numpy version constraint from `<=2.2.6` to `<=2.4.1` to support latest numpy releases
	- Updated all dependencies to latest compatible versions through pixi update
	### Fixed
	- Resolved historical hvplot compatibility issues with numpy 2.x that were preventing updates
	### Technical Details
	- The numpy version limitation was due to binary compatibility issues between numpy 2.0 and hvplot that occurred when numpy 2.0 was released in June 2024
	- These issues have been fully resolved in the ecosystem, with hvplot 0.12.2 now fully compatible with numpy 2.4.x
	- All tests pass successfully with the updated dependencies
	## [1.60.0] - 2026-01-24
	### Changed
	- Updated NumPy version constraint from `<=2.2.6` to `<=2.4.1` to support latest NumPy releases
	- Updated all dependencies to latest compatible versions through pixi update
	### Fixed
	- Resolved historical hvplot compatibility issues with NumPy 2.x that were preventing updates
	### Technical Details
	- The NumPy version limitation was due to binary compatibility issues between NumPy 2.0 and hvplot that occurred when NumPy 2.0 was released in June 2024
	- These issues have been fully resolved in the ecosystem, with hvplot 0.12.2 now fully compatible with NumPy 2.4.x
	- All tests pass successfully with the updated dependencies