pyverge 0.2.0__tar.gz

pyverge-0.2.0/.editorconfig

@@ -0,0 +1,15 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.py]
+indent_size = 4
+indent_style = space
+
+[*.{md,yaml,yml,toml,json}]
+indent_size = 2
+indent_style = space

pyverge-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+name: CI
+
+on:
+  pull_request:
+    branches: [main]
+  push:
+    branches: [main]
+
+env:
+  UV_FROZEN: "1"
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7.0.1
+        with:
+          fetch-depth: 0
+      - uses: astral-sh/setup-uv@v10.0.1
+        with:
+          python-version: "3.11"
+      - run: uv sync --group dev --all-extras
+      - run: uv run pre-commit run --all-files
+      - name: Check conventional commits
+        if: github.event_name == 'pull_request'
+        run: |
+          BASE=$(git merge-base origin/main HEAD)
+          uv run cz check --rev-range "$BASE..HEAD"
+      - name: Validate changelog (dry-run)
+        if: github.event_name == 'pull_request'
+        run: |
+          uv run cz changelog --dry-run

pyverge-0.2.0/.github/workflows/release.yml

@@ -0,0 +1,141 @@
+name: GitHub Release
+
+on:
+  workflow_dispatch:
+  pull_request:
+    types:
+      - closed
+    branches:
+      - main
+
+concurrency:
+  group: release-${{ github.ref }}
+  cancel-in-progress: false
+
+jobs:
+  tag:
+    if: ${{ github.event_name == 'workflow_dispatch' || github.event.pull_request.merged == true }}
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      packages: write
+    steps:
+      - uses: actions/checkout@v7.0.1
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.PUBLISHING_PAT }}
+      - uses: astral-sh/setup-uv@v10.0.1
+        with:
+          python-version: "3.11"
+      - run: uv sync --group dev --all-extras
+      - name: Extract ticket ID from latest commit
+        run: |
+          TICKET_ID=$(git log -1 --pretty=format:"%s" | grep -oE "#[0-9]+" | head -1)
+          if [ -z "$TICKET_ID" ]; then
+            echo "No ticket ID found in latest commit. Aborting."
+            exit 1
+          fi
+          echo "TICKET_ID=$TICKET_ID" >> "$GITHUB_ENV"
+          echo "ticket_id=$TICKET_ID"
+      - name: Bump version, changelog, and tag
+        id: version
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+          # Remember the previous tag so we can list the changes in this release
+          PREV_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
+
+          uv run cz bump --yes --changelog --bump-message "chore(${{ env.TICKET_ID }}): release \$new_version [skip ci]"
+
+          VERSION=$(git describe --tags --abbrev=0)
+          echo "version=$VERSION" >> "$GITHUB_OUTPUT"
+          echo "next_version=$VERSION"
+
+          # Build a human-readable list of changes since the previous release
+          if [ -n "$PREV_TAG" ] && [ "$PREV_TAG" != "$VERSION" ]; then
+            FEATURES=$(git log --no-merges --pretty=format:"- %s" "$PREV_TAG..HEAD~1" || true)
+          else
+            FEATURES="No previous tag found."
+          fi
+          [ -z "$FEATURES" ] && FEATURES="- No conventional changes since last release."
+
+          # Amend the release commit so it actually describes what was deployed
+          git commit --amend \
+            -m "chore(${{ env.TICKET_ID }}): release $VERSION [skip ci]" \
+            -m "Features deployed:" \
+            -m "$FEATURES"
+
+          # Move the lightweight version tag to the amended commit
+          git tag -f "$VERSION"
+
+          git push origin HEAD
+          git push origin "$VERSION" --force
+      - name: Build package
+        run: uv build
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v7.0.1
+        with:
+          name: dist
+          path: dist/
+          if-no-files-found: error
+    outputs:
+      version: ${{ steps.version.outputs.version }}
+
+  release:
+    needs: tag
+    if: ${{ needs.tag.outputs.version != 'none' && needs.tag.outputs.version != '' }}
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      packages: write
+    steps:
+      - uses: actions/checkout@v7.0.1
+        with:
+          fetch-depth: 0
+          ref: ${{ needs.tag.outputs.version }}
+      - uses: astral-sh/setup-uv@v10.0.1
+        with:
+          python-version: "3.11"
+      - run: uv sync --group dev --all-extras
+      - name: Download build artifacts
+        uses: actions/download-artifact@v8.0.1
+        with:
+          name: dist
+          path: dist/
+      - name: Generate release notes
+        run: uv run cz changelog "${{ needs.tag.outputs.version }}" > RELEASE_NOTES.md
+      - name: Create GitHub Release
+        env:
+          GH_TOKEN: ${{ secrets.PUBLISHING_PAT }}
+        run: |
+          gh release create "${{ needs.tag.outputs.version }}" \
+            --title "Release ${{ needs.tag.outputs.version }}" \
+            --notes-file RELEASE_NOTES.md \
+            dist/*
+
+  publish:
+    needs: [tag, release]
+    if: ${{ needs.tag.outputs.version != 'none' && needs.tag.outputs.version != '' }}
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - uses: actions/checkout@v7.0.1
+        with:
+          fetch-depth: 0
+          ref: ${{ needs.tag.outputs.version }}
+      - uses: astral-sh/setup-uv@v10.0.1
+        with:
+          python-version: "3.11"
+      - run: uv sync --group dev --all-extras
+      - name: Download build artifacts
+        uses: actions/download-artifact@v8.0.1
+        with:
+          name: dist
+          path: dist/
+      - name: Publish to PyPI
+        env:
+          UV_PUBLISH_URL: https://upload.pypi.org/legacy/
+          UV_PUBLISH_TOKEN: ${{ secrets.PYPI_TOKEN }}
+        run: uv publish dist/*

pyverge-0.2.0/.gitignore

@@ -0,0 +1,225 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# Hatch vcs
+src/pyverge/_version.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer,
+#   you could uncomment the following to ignore the entire vscode folder
+.vscode/
+.zed/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# Hatch-vcs generated version file
+src/pydantic_migrator/_version.py
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

pyverge-0.2.0/.pre-commit-config.yaml

@@ -0,0 +1,46 @@
+repos:
+  - repo: local
+    hooks:
+      - id: ruff-format
+        name: ruff format
+        entry: uv run ruff format
+        language: system
+        types_or: [python, pyi]
+      - id: ruff-check
+        name: ruff check
+        entry: uv run ruff check
+        language: system
+        types_or: [python, pyi]
+      - id: toml-sort
+        name: toml sort
+        entry: uv run toml-sort --in-place
+        language: system
+        types: [toml]
+      - id: ty
+        name: ty check
+        entry: uv run ty check
+        always_run: true
+        language: system
+        pass_filenames: false
+        types: [python, pyi]
+      - id: pytest
+        name: pytest
+        entry: uv run pytest -vv
+        language: system
+        pass_filenames: false
+        stages: [pre-push]
+  - repo: https://github.com/commitizen-tools/commitizen
+    rev: v4.4.1
+    hooks:
+      - id: commitizen
+        stages: [commit-msg]
+  - repo: https://github.com/rhysd/actionlint
+    rev: v1.7.12
+    hooks:
+      - id: actionlint
+        stages: [pre-commit]
+        types: [yaml]
+        pass_filenames: true
+ci:
+  skip:
+    - commitizen

pyverge-0.2.0/CHANGELOG.md

@@ -0,0 +1,64 @@
+## v0.2.0 (2026-08-18)
+
+### Feat
+
+- **#42**: include deployed changes in release commit body
+
+### Fix
+
+- **#42**: publish release artifacts to PyPI
+- **#42**: migrate release workflow from Node 20 actions
+
+## v0.1.3 (2026-08-17)
+
+### Fix
+
+- **#42**: escape $new_version in cz bump message
+
+## v0.1.2 (2026-08-18)
+
+### Fix
+
+- **#42**: use correct cz bump placeholder
+- **#42**: merge publish back into release workflow
+- **#42**: use correct version placeholder in cz bump message
+- **#42**: fix uv publish command syntax
+
+## v0.1.1 (2026-08-18)
+
+### Fix
+
+- **#42**: fix uv publish command syntax
+
+## v0.1.0 (2026-08-18)
+
+### Feat
+
+- **#42**: release (#43)
+- **#40**: policy (#41)
+- add ModelManager lookup helpers (#32)
+- **#38**: cli (#39)
+- **#24**: docs (#29)
+- **#19**: manager (#28)
+- **#17**: engine (#18)
+- **#12**: versioning (#16)
+- **#12**: registry (#13) - introduced registry
+- **#10**: versioning (#11)
+- **#1**: Add pydantic-migrator (#4)
+- **#1**: Add pydantic-migrator package
+- **#1**: Add tests
+- **#1**: Add pytest and syrupy
+- **#1**: Add ci workflow
+- **#1**: Add project configurations
+
+### Fix
+
+- **#33**: pre commit (#37)
+- **#33**: migration (#36)
+- **#33**: core (#35)
+- **#33**: versioning (#34)
+- **#30**: typed migration (#31)
+
+### Refactor
+
+- **#7**: remove Avro, Protobuf, and TypeScript export (#8)

pyverge-0.2.0/CONTRIBUTING.md

@@ -0,0 +1,97 @@
+# Contributing to pyverge
+
+Thank you for considering contributing to pyverge! This document outlines the
+process for contributing code, documentation, and ideas.
+
+## Getting started
+
+1. **Fork the repository** and clone it locally.
+2. **Create a virtual environment** and install dependencies:
+   ```bash
+   uv sync --dev
+   ```
+3. **Run the tests** to ensure everything works:
+   ```bash
+   uv run pytest
+   ```
+
+## How to contribute
+
+### Reporting issues
+
+- Use the issue tracker to report bugs, request features, or ask questions.
+- For bugs, include:
+  - A minimal reproducible example
+  - Expected vs. actual behavior
+  - Python version and pyverge version
+  - Stack traces if applicable
+
+### Submitting code
+
+1. **Create a branch** from `main`:
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+
+2. **Make your changes** following the existing code style.
+
+3. **Write tests** for new functionality. Aim for high coverage.
+
+4. **Run checks** before committing:
+   ```bash
+   uv run ruff check .
+   uv run ruff format .
+   uv run pytest
+   uv run ty check src/pyverge
+   ```
+
+5. **Commit** with a clear message following [Conventional Commits](https://www.conventionalcommits.org/):
+   ```bash
+   git commit -m "feat: add new migration hook type"
+   ```
+
+6. **Push** and open a pull request.
+
+### Documentation
+
+- Documentation lives in `docs/`.
+- Use reStructuredText or Markdown consistently.
+- Include examples for new features.
+- Update the changelog if applicable.
+
+## Code style
+
+- **Formatting**: `ruff format` (Black-compatible)
+- **Linting**: `ruff check`
+- **Type checking**: `ty check`
+- **Testing**: `pytest` with `-vv` for verbose output
+
+Follow existing patterns in the codebase. When in doubt, match the surrounding
+code.
+
+## Pull request process
+
+1. **CI must pass** — all checks (ruff, ty, pytest) must be green.
+2. **Review** — at least one maintainer must approve.
+3. **Squash** — if your branch has multiple commits, squash them into logical
+   units before merging.
+4. **Merge** — maintainers will merge your PR once approved.
+
+## Release process
+
+Releases are automated via [commitizen](https://commitizen-tools.github.io/commitizen/):
+
+1. Commit messages determine the next version:
+   - `feat:` → minor version bump
+   - `fix:` → patch version bump
+   - `BREAKING CHANGE:` → major version bump
+
+2. Pushing to `main` triggers the release pipeline.
+
+3. The changelog is auto-generated from commit messages.
+
+## Questions?
+
+- Open an issue for discussion.
+- Check existing issues and PRs for similar topics.
+- Read the [documentation](docs/) for usage guidance.