refactor: use uv and poe for everything

Author: theagenticguy

.github/workflows/integration-test.yml

@@ -60,14 +60,17 @@ jobs:
         uses: actions/setup-python@v5
         with:
           python-version: '3.10'
-      - name: Install dependencies
-        run: |
-          pip install --no-cache-dir hatch
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          enable-cache: true
+      - name: Sync dependencies from lock file
+        run: uv sync --dev
       - name: Run integration tests
         env:
           AWS_REGION: us-east-1
           AWS_REGION_NAME: us-east-1 # Needed for LiteLLM
           STRANDS_TEST_API_KEYS_SECRET_NAME: ${{ secrets.STRANDS_TEST_API_KEYS_SECRET_NAME }}
         id: tests
         run: |
-          hatch test tests_integ
+          uv run poe test-integ

.github/workflows/pypi-publish-on-release.yml

@@ -34,7 +34,7 @@ jobs:
     - name: Install dependencies
       run: |
         python -m pip install --upgrade pip
-        pip install hatch twine
+        pip install hatch twine  # Keep hatch for versioning and building
 
     - name: Validate version
       run: |

.github/workflows/test-lint.yml

@@ -59,12 +59,15 @@ jobs:
         uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
-      - name: Install dependencies
-        run: |
-          pip install --no-cache-dir hatch
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          enable-cache: true
+      - name: Sync dependencies from lock file
+        run: uv sync --dev
       - name: Run Unit tests
         id: tests
-        run: hatch test tests --cover
+        run: uv run poe test-cov
         continue-on-error: false
   lint:
     name: Lint
@@ -82,13 +85,16 @@ jobs:
         uses: actions/setup-python@v5
         with:
           python-version: '3.10'
-          cache: 'pip'
 
-      - name: Install dependencies
-        run: |
-          pip install --no-cache-dir hatch
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          enable-cache: true
+
+      - name: Sync dependencies from lock file
+        run: uv sync --dev
 
       - name: Run lint
         id: lint
-        run: hatch run test-lint
+        run: uv run poe lint-check
         continue-on-error: false

.pre-commit-config.yaml

@@ -1,36 +1,36 @@
 repos:
   - repo: local
     hooks:
-      - id: hatch-format
-        name: Format code
-        entry: hatch fmt --formatter
+      - id: format-check
+        name: Check code formatting
+        entry: uv run poe format-check
         language: system
         pass_filenames: false
         types: [python]
         stages: [pre-commit]
-      - id: hatch-lint
-        name: Lint code
-        entry: hatch run test-lint
+      - id: lint-check
+        name: Check code linting
+        entry: uv run poe lint-check
         language: system
         pass_filenames: false
         types: [python]
         stages: [pre-commit]
-      - id: hatch-test-lint
-        name: Type linting
-        entry: hatch run test-lint
+      - id: typecheck
+        name: Type checking
+        entry: uv run poe typecheck
         language: system
         pass_filenames: false
-        types: [ python ]
-        stages: [ pre-commit ]
-      - id: hatch-test
+        types: [python]
+        stages: [pre-commit]
+      - id: test
         name: Unit tests
-        entry: hatch test
+        entry: uv run poe test
         language: system
         pass_filenames: false
         types: [python]
         stages: [pre-commit]
       - id: commitizen-check
         name: Check commit message
-        entry: hatch run cz check --commit-msg-file
+        entry: uv run cz check --commit-msg-file
         language: system
-        stages: [commit-msg]
+        stages: [commit-msg]

CONTRIBUTING.md

@@ -130,6 +130,67 @@ You can check:
 - Feature requests in [Feature Requests](../../issues?q=is%3Aissue%20state%3Aopen%20label%3Aenhancement) for new functionality to implement
 
 
+## Dependency Management with uv lock
+
+This project uses `uv lock` to ensure reproducible dependency resolution across all environments. The `uv.lock` file contains exact versions of all dependencies and **must be committed to git**.
+
+### For Developers
+
+**Initial Setup:**
+```bash
+# Install exact dependencies from lock file
+uv sync --dev
+```
+
+**Daily Development:**
+```bash
+# Use locked dependencies for all commands
+uv run poe test
+uv run poe lint
+uv run poe format
+```
+
+**Adding New Dependencies:**
+```bash
+# Add new dependency and update lock file
+uv add "new-package>=1.0.0"
+# The lock file is automatically updated
+git add pyproject.toml uv.lock
+git commit -m "feat: add new-package dependency"
+```
+
+**Updating Dependencies:**
+```bash
+# Update to latest compatible versions
+uv lock
+
+# Or upgrade to latest versions (major updates)
+uv lock --upgrade
+
+# Always commit lock file changes
+git add uv.lock
+git commit -m "chore: update dependencies"
+```
+
+### Why Lock Files Matter
+
+- **Reproducible Builds**: Same exact dependencies across dev, CI, and production
+- **Faster CI**: Pre-resolved dependencies eliminate resolution time
+- **Security**: Pinned versions prevent supply chain attacks
+- **Team Consistency**: Everyone gets identical dependency trees
+
+### Lock File Commands
+
+| Command | Purpose |
+|---------|---------|
+| `uv sync --dev` | Install exact dependencies from lock file |
+| `uv sync` | Install production dependencies only |
+| `uv lock` | Update lock file with latest compatible versions |
+| `uv lock --upgrade` | Upgrade all dependencies to latest versions |
+
+**Important**: Always commit `uv.lock` changes alongside `pyproject.toml` changes!
+
+
 ## Code of Conduct
 This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
 For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact