vet

commit b44071c37f5fb915bc3d140e1f890a8c76593f16
parent f7128771fab84690fc85d51655630c903a8424fc
Author: andrewlaack-collab <andrew.laack@imbue.com>
Date:   Thu, 12 Feb 2026 23:11:56 +0000

Bump v0.1.5 (#74)

* Updated development messaging

* Updated pyproject version

* Bumped to 0.1.5
Diffstat:
M
DEVELOPMENT.md
 | 
11
++++++-----
M
README.md
 | 
2
+-
M
pyproject.toml
 | 
2
+-

3 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md
@@ -52,17 +52,18 @@ Vet is published to PyPI via the `publish-to-pypi.yml` GitHub Actions workflow. 
 ### Releasing a new version
 
 1. Update the version in `pyproject.toml`
-2. Commit and push the change
+3. Update the recommended GitHub action pinned version in the `README.md` 
+   ```yaml
+   - run: pip install verify-everything==0.2.0
+   ```
+2. Commit and push the changes
 3. Tag the commit and push the tag:
    ```bash
    git tag v0.2.0 -m "v0.2.0: Updated XYZ"
    git push origin v0.2.0
    ```
 4. The `Publish to PyPI` workflow will automatically build and publish the package
-5. Update the recommended GitHub action pinned version in the `README.md` 
-   ```yaml
-   - run: pip install verify-everything==0.2.0
-   ```
+5. Merge PR into main.
 
 ### Why pin the version in the README?
 
diff --git a/README.md b/README.md
@@ -90,7 +90,7 @@ jobs:
       - uses: actions/setup-python@v5
         with:
           python-version: "3.11"
-      - run: pip install verify-everything==0.1.4
+      - run: pip install verify-everything==0.1.5
       - name: Run vet
         if: github.event.pull_request.head.repo.full_name == github.repository
         env:
diff --git a/pyproject.toml b/pyproject.toml
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "verify-everything"
-version = "0.1.4"
+version = "0.1.5"
 description = "LLM-based code review tool that finds issues tests and linters miss"
 readme = "README.md"
 license = "AGPL-3.0-only"