Refactor/internal pipeline v2

.github/workflows/tests.yml

@@ -15,15 +15,23 @@ jobs:
           - "3.12"
           - "3.13"
           - "3.14-dev"
+
     steps:
       - uses: actions/checkout@v4
+
       - name: Set up Python
         uses: actions/setup-python@v5
         with:
-          python-version:  ${{ matrix.python }}
+          python-version: ${{ matrix.python }}
+
       - name: Install toolchain
-        run: pip install ruff
+        run: pip install ruff==0.13.2 pytest
+
+      - name: Install package
+        run: pip install -e .
+
       - name: Unit tests
-        run: python -m unittest tests/*/*.py
+        run: python -m pytest
+
       - name: Lint
         run: ruff check secure tests

CHANGELOG.md

@@ -9,7 +9,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Placeholder for upcoming changes.
 
-## [2.0.0] - 2025-12-13
+## [2.0.1] - 2026-04-21
+
+This is the first stable v2 release. Version `2.0.0` was burned and should be skipped when tagging or publishing.
 
 ### Breaking Changes
 
@@ -27,7 +29,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Docs
 
-- Expanded README with usage examples, advanced pipeline guidance, and updated framework integration references.
+- Expanded README with usage examples, advanced pipeline guidance, updated framework integration references, and v2 migration guidance.
 
 ## [1.0.1] - 2024-10-18
 

CONTRIBUTING.md

@@ -15,13 +15,13 @@ Thanks for helping make `secure` better. The following guidance keeps contributi
    ```
 3. Install the tooling used by the project:
    ```bash
-   pip install ruff
+   pip install pytest ruff
    ```
-   _Optional:_ `uv` is the package manager used by the project for releases; you can use `uv add ...` to manage dependencies, but it is not required for local development.
+   _Optional:_ `uv` is the package manager used by the project for releases; you can use `uv run pytest` and `uv add ...` to manage dependencies, but it is not required for local development.
 
 ## Running tests, linting, and formatting
 
-- **Run unit tests:** `python -m unittest tests/*/*.py`
+- **Run unit tests:** `pytest`
 - **Run the linter:** `ruff check`
 - **Apply formatting / fix issues:** `ruff format`
 
@@ -57,7 +57,7 @@ Run these commands before opening a pull request. If you rely on a different Pyt
 
 ## Pull request checklist
 
-- [ ] I have run `python -m unittest tests/*/*.py` locally (or a representative suite) and addressed any failures.
+- [ ] I have run `pytest` locally (or a representative suite) and addressed any failures.
 - [ ] I have run `ruff check` and `ruff format` (when formatting attr).
 - [ ] Documentation updates describe the new behavior (new header docs, framework guidance, etc.).
 - [ ] If applicable, I have updated the release notes/CHANGELOG entry for new user-visible behavior.