valid8r 0.7.1__tar.gz → 0.7.2__tar.gz

{valid8r-0.7.1 → valid8r-0.7.2}/.github/CONVENTIONAL_COMMITS.md

@@ -25,7 +25,7 @@ This is a quick reference guide for writing conventional commits for the valid8r
 | `test` | 🔼 **patch** | Adding or updating tests | `test: add edge cases for validators` |
 | `chore` | 🔼 **patch** | Maintenance tasks | `chore: update dependencies` |
 | `ci` | ⚪ **none** | CI/CD changes | `ci: add Python 3.13 to matrix` |
-| `build` | ⚪ **none** | Build system changes | `build: update poetry config` |
+| `build` | ⚪ **none** | Build system changes | `build: update uv config` |
 
 ## Breaking Changes (Major Bump)
 
@@ -268,9 +268,9 @@ Before committing, check:
 
 ```bash
 # Run checks before committing
-poetry run ruff check .
-poetry run mypy valid8r
-poetry run pytest
+uv run ruff check .
+uv run mypy valid8r
+uv run pytest
 
 # Then commit
 git commit -m "feat(parsers): add parse_phone_number"

{valid8r-0.7.1 → valid8r-0.7.2}/.github/QUICK_REFERENCE.md

@@ -31,9 +31,9 @@ git commit -m "feat(parsers): add phone validation"
 gh pr create --fill
 
 # Run checks locally
-poetry run pytest
-poetry run mypy valid8r
-poetry run ruff check .
+uv run pytest
+uv run mypy valid8r
+uv run ruff check .
 ```
 
 ### Manual Workflow Triggers

{valid8r-0.7.1 → valid8r-0.7.2}/.github/README.md

@@ -184,9 +184,9 @@ git checkout -b feat/add-parser
 # ... edit code ...
 
 # 3. Run tests locally
-poetry run pytest
-poetry run mypy valid8r
-poetry run ruff check .
+uv run pytest
+uv run mypy valid8r
+uv run ruff check .
 
 # 4. Commit with conventional format
 git commit -m "feat(parsers): add phone number parser"
@@ -284,11 +284,11 @@ gh workflow run stale.yml
 
 **Run locally**:
 ```bash
-poetry run ruff check .
-poetry run ruff format --check .
-poetry run mypy valid8r
-poetry run pytest
-poetry run behave tests/bdd/features
+uv run ruff check .
+uv run ruff format --check .
+uv run mypy valid8r
+uv run pytest
+uv run behave tests/bdd/features
 ```
 
 Fix issues and push again.

{valid8r-0.7.1 → valid8r-0.7.2}/.github/SETUP_CHECKLIST.md

@@ -121,17 +121,16 @@ Create `test-pypi` environment (optional):
 
 ```bash
 # Ensure version is 0.1.0 in pyproject.toml
-poetry version 0.1.0
+# Version is managed by semantic-release, but for first publish verify it's set correctly
 
 # Build the package
-poetry build
+uv build
 
 # Publish to Test PyPI first (to verify)
-poetry config repositories.testpypi https://test.pypi.org/legacy/
-poetry publish -r testpypi --username __token__ --password pypi-...
+uv publish --publish-url https://test.pypi.org/legacy/ --token pypi-...
 
 # If test publish succeeds, publish to production PyPI
-poetry publish --username __token__ --password pypi-...
+uv publish --token pypi-...
 ```
 
 **Option B: Trusted Publisher** (More secure, no tokens needed)
@@ -219,8 +218,9 @@ Final verification checklist:
 **Expected behavior**: The workflow skips publishing if version exists.
 
 **If you need to republish**:
-1. Bump version manually: `poetry version patch`
-2. Commit and push to trigger new release
+1. Version bump happens automatically via semantic-release based on conventional commits
+2. Commit with appropriate conventional commit type and push to trigger new release
+3. Or manually trigger version bump: `gh workflow run semantic-release.yml`
 
 ### Issue: Required checks not appearing in branch protection
 

{valid8r-0.7.1 → valid8r-0.7.2}/.github/WORKFLOWS.md

@@ -240,7 +240,7 @@ vim valid8r/core/parsers.py
 vim tests/unit/test_parsers.py
 
 # Run tests locally
-poetry run pytest
+uv run pytest
 
 # Commit with conventional format
 git add .
@@ -386,11 +386,11 @@ gh workflow run version-and-release.yml -f version_bump=patch
 1. Check workflow run logs in GitHub Actions tab
 2. Run same checks locally:
    ```bash
-   poetry run ruff check .
-   poetry run ruff format --check .
-   poetry run mypy valid8r
-   poetry run pytest
-   poetry run behave tests/bdd/features
+   uv run ruff check .
+   uv run ruff format --check .
+   uv run mypy valid8r
+   uv run pytest
+   uv run behave tests/bdd/features
    ```
 3. Fix issues and push again
 

{valid8r-0.7.1 → valid8r-0.7.2}/.github/pull_request_template.md

@@ -31,7 +31,7 @@ Fixes #
 
 - [ ] Unit tests added/updated
 - [ ] BDD tests added/updated (if applicable)
-- [ ] All tests pass locally (`poetry run tox`)
+- [ ] All tests pass locally (`uv run tox`)
 - [ ] Test coverage maintained or improved
 
 ## Test Evidence
@@ -40,7 +40,7 @@ Fixes #
 
 ```
 # Example:
-$ poetry run pytest tests/unit/test_my_feature.py
+$ uv run pytest tests/unit/test_my_feature.py
 ================================ test session starts =================================
 collected 15 items
 
@@ -52,9 +52,9 @@ tests/unit/test_my_feature.py ............... [100%]
 
 ## Checklist
 
-- [ ] Code follows the project's style guidelines (`poetry run ruff check .`)
-- [ ] Code is formatted properly (`poetry run ruff format .`)
-- [ ] Type hints are complete and pass mypy (`poetry run mypy valid8r`)
+- [ ] Code follows the project's style guidelines (`uv run ruff check .`)
+- [ ] Code is formatted properly (`uv run ruff format .`)
+- [ ] Type hints are complete and pass mypy (`uv run mypy valid8r`)
 - [ ] Docstrings added/updated for public API
 - [ ] `__all__` exports updated if public API changed
 - [ ] CLAUDE.md updated if architecture/patterns changed
@@ -72,7 +72,7 @@ N/A
 - [ ] README.md updated (if needed)
 - [ ] API documentation updated (docstrings)
 - [ ] Usage examples added (if new feature)
-- [ ] Sphinx docs build successfully (`poetry run docs-build`)
+- [ ] Sphinx docs build successfully (`uv run docs-build`)
 
 # Additional Notes
 

{valid8r-0.7.1 → valid8r-0.7.2}/.readthedocs.yaml

@@ -10,14 +10,12 @@ build:
   tools:
     python: "3.11"
   commands:
-    # Install poetry
-    - pip install poetry
-    # Configure poetry to not create virtualenvs
-    - poetry config virtualenvs.create false
+    # Install uv
+    - pip install uv
     # Install all dependencies including the project itself
-    - poetry install --with docs --no-interaction
-    # Let Poetry run Sphinx to avoid dependency conflicts
-    - poetry run sphinx-build -b html docs $READTHEDOCS_OUTPUT/html
+    - uv sync --group docs
+    # Let uv run Sphinx to avoid dependency conflicts
+    - uv run sphinx-build -b html docs $READTHEDOCS_OUTPUT/html
 
 # Build documentation formats
 formats:

{valid8r-0.7.1 → valid8r-0.7.2}/CLAUDE.md

@@ -77,7 +77,11 @@ All new features MUST follow this exact workflow using the specialized agents de
 
 ## Common Development Commands
 
-**Note**: This project uses `uv` for dependency management (not Poetry). Install it with:
+**Note**: This project uses `uv` for dependency management. The migration from Poetry to uv was completed in November 2025 (PR #48), bringing 60% faster CI pipelines and 300x+ faster dependency resolution.
+
+See `docs/migration-poetry-to-uv.md` for the complete migration guide, including command comparisons and troubleshooting.
+
+**Install uv:**
 ```bash
 curl -LsSf https://astral.sh/uv/install.sh | sh
 ```
@@ -156,15 +160,22 @@ uv run python smoke_test.py
 
 ### Dependency Management
 ```bash
-# Add a new dependency
+# Add a production dependency
 uv add requests
 
 # Add a dev dependency
-uv add --dev pytest-timeout
+uv add --group dev pytest-timeout
+
+# Add to specific dependency groups
+uv add --group test pytest-mock
+uv add --group docs sphinx-theme
 
 # Update all dependencies
 uv lock --upgrade
 
+# Update a specific package
+uv lock --upgrade-package requests
+
 # Export requirements for other tools
 uv export > requirements.txt
 ```

{valid8r-0.7.1 → valid8r-0.7.2}/CONTRIBUTING.md

@@ -24,8 +24,8 @@ This project adheres to the [Contributor Covenant Code of Conduct](CODE_OF_CONDU
 
 ### Prerequisites
 
-- Python 3.11 or higher
-- [Poetry](https://python-poetry.org/) for dependency management
+- Python 3.11 or higher (3.11-3.14 supported)
+- [uv](https://docs.astral.sh/uv/) for dependency management (10-100x faster than Poetry)
 - [pyenv](https://github.com/pyenv/pyenv) (recommended for managing Python versions)
 - Git
 
@@ -56,24 +56,32 @@ pyenv install 3.14.0
 pyenv local 3.11.11 3.12.9 3.13.5 3.14.0
 ```
 
-### 2. Install Poetry
+### 2. Install uv
 
 ```bash
-curl -sSL https://install.python-poetry.org | python3 -
+curl -LsSf https://astral.sh/uv/install.sh | sh
+```
+
+**Verify installation:**
+```bash
+uv --version
+# Should show: uv 0.9.x or later
 ```
 
 ### 3. Install Dependencies
 
 ```bash
-poetry install
+uv sync
 ```
 
 This installs all dependencies including dev, test, lint, and docs groups.
 
+**Note**: If you previously used Poetry, see [docs/migration-poetry-to-uv.md](../docs/migration-poetry-to-uv.md) for migration instructions.
+
 ### 4. Set Up Pre-commit Hooks
 
 ```bash
-poetry run pre-commit install
+uv run pre-commit install
 ```
 
 Pre-commit hooks automatically:
@@ -101,16 +109,16 @@ Write clean, well-tested code following our style guidelines.
 
 ```bash
 # Run all tests with coverage
-poetry run tox
+uv run tox
 
 # Run only unit tests
-poetry run pytest tests/unit
+uv run pytest tests/unit
 
 # Run BDD tests
-poetry run tox -e bdd
+uv run tox -e bdd
 
 # Run linting
-poetry run tox -e lint
+uv run tox -e lint
 ```
 
 ### 4. Commit Your Changes
@@ -145,13 +153,13 @@ Then create a Pull Request on GitHub.
 
 ```bash
 # Format code with ruff
-poetry run ruff format .
+uv run ruff format .
 
 # Check and fix linting issues
-poetry run ruff check . --fix
+uv run ruff check . --fix
 
 # Check type hints
-poetry run mypy valid8r
+uv run mypy valid8r
 ```
 
 ### Code Patterns
@@ -312,7 +320,7 @@ See [.github/CONVENTIONAL_COMMITS.md](.github/CONVENTIONAL_COMMITS.md) for more
 
 ### Before Submitting
 
-1. Ensure all tests pass: `poetry run tox`
+1. Ensure all tests pass: `uv run tox`
 2. Update documentation if needed
 3. Add changelog entry if applicable
 4. Verify your commits follow the conventional commit format
@@ -403,10 +411,10 @@ def parse_email(text: str) -> Maybe[EmailAddress]:
 
 ```bash
 # Build documentation
-poetry run docs-build
+uv run docs-build
 
 # Serve with live reload
-poetry run docs-serve
+uv run docs-serve
 ```
 
 View at http://localhost:8000
@@ -431,17 +439,17 @@ View at http://localhost:8000
 
 ```bash
 # Run smoke test
-python smoke_test.py
+uv run python smoke_test.py
 
 # Check coverage
-poetry run pytest --cov=valid8r --cov-report=html tests/unit
+uv run pytest --cov=valid8r --cov-report=html tests/unit
 # View at htmlcov/index.html
 
 # Run specific test
-poetry run pytest tests/unit/test_parsers.py::DescribeParseInt::it_parses_positive_integers
+uv run pytest tests/unit/test_parsers.py::DescribeParseInt::it_parses_positive_integers
 
 # Watch mode (requires pytest-watch)
-poetry run ptw tests/unit
+uv run ptw tests/unit
 ```
 
 ### Debugging

{valid8r-0.7.1 → valid8r-0.7.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: valid8r
-Version: 0.7.1
+Version: 0.7.2
 Summary: Clean, flexible input validation for Python applications
 Project-URL: Homepage, https://valid8r.readthedocs.io/
 Project-URL: Repository, https://github.com/mikelane/valid8r
@@ -269,28 +269,36 @@ For more examples, see the [documentation](https://valid8r.readthedocs.io/).
 
 ## Development
 
-This project uses Poetry for dependency management and Tox for testing.
+This project uses `uv` for fast dependency management and `tox` for testing across Python versions.
 
 ### Setup
 
 ```bash
-# Install Poetry
-curl -sSL https://install.python-poetry.org | python3 -
+# Install uv
+curl -LsSf https://astral.sh/uv/install.sh | sh
 
 # Install dependencies
-poetry install
+uv sync
 ```
 
 ### Running Tests
 
 ```bash
 # Run all tests
-poetry run tox
+uv run tox
+
+# Run unit tests only
+uv run pytest tests/unit
 
 # Run BDD tests
-poetry run tox -e bdd
+uv run tox -e bdd
+
+# Run with coverage
+uv run pytest --cov=valid8r tests/unit
 ```
 
+See [docs/migration-poetry-to-uv.md](docs/migration-poetry-to-uv.md) for the complete migration guide and command reference.
+
 ## License
 
 This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.

{valid8r-0.7.1 → valid8r-0.7.2}/README.md

@@ -238,28 +238,36 @@ For more examples, see the [documentation](https://valid8r.readthedocs.io/).
 
 ## Development
 
-This project uses Poetry for dependency management and Tox for testing.
+This project uses `uv` for fast dependency management and `tox` for testing across Python versions.
 
 ### Setup
 
 ```bash
-# Install Poetry
-curl -sSL https://install.python-poetry.org | python3 -
+# Install uv
+curl -LsSf https://astral.sh/uv/install.sh | sh
 
 # Install dependencies
-poetry install
+uv sync
 ```
 
 ### Running Tests
 
 ```bash
 # Run all tests
-poetry run tox
+uv run tox
+
+# Run unit tests only
+uv run pytest tests/unit
 
 # Run BDD tests
-poetry run tox -e bdd
+uv run tox -e bdd
+
+# Run with coverage
+uv run pytest --cov=valid8r tests/unit
 ```
 
+See [docs/migration-poetry-to-uv.md](docs/migration-poetry-to-uv.md) for the complete migration guide and command reference.
+
 ## License
 
 This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.

{valid8r-0.7.1 → valid8r-0.7.2}/docs/development/contributing.rst

@@ -17,23 +17,26 @@ Setting Up Your Development Environment
       git clone https://github.com/your-username/valid8r.git
       cd valid8r
 
-3. **Set up Poetry**
+3. **Set up uv**
 
-   Valid8r uses Poetry for dependency management. Make sure you have Poetry installed:
+   Valid8r uses uv for fast dependency management. Make sure you have uv installed:
 
    .. code-block:: bash
 
-      # Install Poetry if you don't have it
-      curl -sSL https://install.python-poetry.org | python3 -
+      # Install uv if you don't have it
+      curl -LsSf https://astral.sh/uv/install.sh | sh
+
+      # Verify installation
+      uv --version
 
       # Install dependencies
-      poetry install
+      uv sync
 
 4. **Set up pre-commit hooks**
 
    .. code-block:: bash
 
-      poetry run pre-commit install
+      uv run pre-commit install
 
 Development Workflow
 --------------------
@@ -58,26 +61,26 @@ Development Workflow
    .. code-block:: bash
 
       # Run unit tests
-      poetry run pytest tests/unit
+      uv run pytest tests/unit
 
       # Run BDD tests
-      poetry run behave tests/bdd/features
+      uv run behave tests/bdd/features
 
       # Run all tests with tox (multiple Python versions)
-      poetry run tox
+      uv run tox
 
 4. **Check code quality**
 
    .. code-block:: bash
 
       # Run ruff for linting
-      poetry run ruff check .
+      uv run ruff check .
 
       # Run isort to check imports
-      poetry run isort --check-only valid8r tests
+      uv run isort --check-only valid8r tests
 
       # Run mypy for type checking
-      poetry run mypy valid8r
+      uv run mypy valid8r
 
 5. **Commit your changes**
 
@@ -151,10 +154,10 @@ Documentation is a crucial part of Valid8r:
    .. code-block:: bash
 
       # Build documentation
-      poetry run docs-build
+      uv run docs-build
 
       # Serve documentation locally
-      poetry run docs-serve
+      uv run docs-serve
 
 Pull Request Process
 --------------------

{valid8r-0.7.1 → valid8r-0.7.2}/docs/development/testing.rst

@@ -45,42 +45,45 @@ The test directory structure is organized as follows:
 Running Tests
 -------------
 
-You can run tests using Poetry or tox:
+You can run tests using uv or tox:
 
 .. code-block:: bash
 
    # Run all tests with the current Python version
-   poetry run pytest
+   uv run pytest
 
    # Run only unit tests
-   poetry run pytest tests/unit
+   uv run pytest tests/unit
 
    # Run only BDD tests
-   poetry run behave tests/bdd/features
+   uv run behave tests/bdd/features
 
    # Run tests with coverage
-   poetry run pytest --cov=valid8r tests/unit
+   uv run pytest --cov=valid8r tests/unit
 
-   # Run tests across all supported Python versions
-   poetry run tox
+   # Run tests across all supported Python versions (3.11-3.14)
+   uv run tox
 
    # Run tests for a specific Python version
-   poetry run tox -e py313  # primary dev version
-   poetry run tox -e py311  # minimum supported
+   uv run tox -e py313  # primary dev version
+   uv run tox -e py311  # minimum supported
+   uv run tox -e py314  # latest supported
 
    # Run only BDD tests with tox
-   poetry run tox -e bdd
+   uv run tox -e bdd
 
 Continuous Integration
 ----------------------
 
 Valid8r uses GitHub Actions for continuous integration. The CI pipeline runs:
 
-1. Tests across all supported Python versions
+1. Tests across all supported Python versions (3.11, 3.12, 3.13, 3.14)
 2. Code quality checks (ruff, isort, mypy)
 3. Documentation builds
 4. Coverage reporting
 
+The migration to uv has resulted in approximately 60% faster CI pipelines compared to Poetry.
+
 Writing Unit Tests
 ------------------
 
@@ -187,9 +190,9 @@ Valid8r aims for high test coverage. You can generate a coverage report with:
 
 .. code-block:: bash
 
-   poetry run pytest --cov=valid8r tests/
-   poetry run coverage report -m
-   poetry run coverage html
+   uv run pytest --cov=valid8r tests/
+   uv run coverage report -m
+   uv run coverage html
 
 The coverage report in HTML format will be generated in the `htmlcov` directory.
 
@@ -201,16 +204,16 @@ When tests fail, you can use the following options to help debug:
 .. code-block:: bash
 
    # Show print statements during tests
-   poetry run pytest -s
+   uv run pytest -s
 
    # Increase verbosity
-   poetry run pytest -v
+   uv run pytest -v
 
    # Run a specific test
-   poetry run pytest tests/unit/test_maybe.py::DescribeMaybe::it_creates_just_values
+   uv run pytest tests/unit/test_maybe.py::DescribeMaybe::it_creates_just_values
 
    # For BDD tests, run a specific scenario
-   poetry run behave tests/bdd/features/clean_type_parsing.feature:12
+   uv run behave tests/bdd/features/clean_type_parsing.feature:12
 
 Testing Edge Cases
 ------------------

{valid8r-0.7.1 → valid8r-0.7.2}/docs/index.rst

@@ -60,7 +60,13 @@ Installation
 
    pip install valid8r
 
-Alternatively, if you use Poetry:
+Alternatively, if you use uv:
+
+.. code-block:: bash
+
+   uv add valid8r
+
+Or if you use Poetry:
 
 .. code-block:: bash
 

{valid8r-0.7.1 → valid8r-0.7.2}/docs/user_guide/getting_started.rst

@@ -4,13 +4,19 @@ Getting Started
 Installation
 ------------
 
-Valid8r requires Python 3.11 or higher. You can install it using pip:
+Valid8r requires Python 3.11 or higher (supports Python 3.11-3.14). You can install it using pip:
 
 .. code-block:: bash
 
    pip install valid8r
 
-Or, if you use Poetry:
+Or, if you use uv (recommended for faster dependency resolution):
+
+.. code-block:: bash
+
+   uv add valid8r
+
+Or with Poetry:
 
 .. code-block:: bash
 

{valid8r-0.7.1 → valid8r-0.7.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "valid8r"
-version = "0.7.1"
+version = "0.7.2"
 description = "Clean, flexible input validation for Python applications"
 authors = [
     {name = "Mike Lane", email = "mikelane@gmail.com"}

{valid8r-0.7.1 → valid8r-0.7.2}/uv.lock

@@ -1576,7 +1576,7 @@ wheels = [
 
 [[package]]
 name = "valid8r"
-version = "0.7.0"
+version = "0.7.1"
 source = { editable = "." }
 dependencies = [
     { name = "email-validator" },