Cutting an RC for Dependency Work

[johnwalz97]

Pull Request Description

What and why?

How to test

What needs special review?

Dependencies, breaking changes, and deployment notes

Release notes

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

[nibalizer]

what I would do is cut a branch from main and pypi release from that branch

[johnwalz97]

what I would do is cut a branch from main and pypi release from that branch

This is that, I checked out main, created a tag, a pre-release in releases and this PR to be able to publish to PyPi.

[nibalizer]

what I would do is cut a branch from main and pypi release from that branch

This is that, I checked out main, created a tag, a pre-release in releases and this PR to be able to publish to PyPi.

Perfect!

[nibalizer]

@johnwalz97 lets merge this

[cachafla]

Let's merge?

[github-actions]

PR Summary

This PR introduces two main changes:

1. Version updates: The project version has been updated from 2.9.5 to 2.10.0 across the project metadata files. While these version bumps are not the main focus, they help with proper release tracking.

2. Enhanced version parsing: The function parse_version in validmind/utils.py has been refactored to use the packaging.version.Version class. This improves the robustness and correctness when processing version strings, ensuring that the returned tuple correctly represents the major, minor, and micro components of the input version.

Additionally, minor formatting changes in the GitHub Actions workflow file (pypi.yaml) have been made to standardize quote usage for consistency.

Test Suggestions

• Add unit tests for parse_version with a variety of version strings, including edge cases and non-standard formats.
• Verify that parse_version correctly parses versions with leading/trailing whitespace or pre-release/build metadata.
• Run integration tests to ensure that projects depending on validmind continue functioning correctly with the new version parsing logic.
• Confirm that the GitHub workflow correctly installs dependencies and uses the specified version of Python.