chore(release): prepare 0.2.1

[sathariels]

Summary

Prepare jevcheck 0.2.1. This pull request does not push a git tag, open a GitHub Release, or upload to PyPI. Those steps are in RELEASING.md and below. Documented Action refs pin @v0.2.1. That tag does not exist until it is created on the merge commit, so those uses: refs resolve only after that tag is pushed.

Library source since 0.2.0 is the version string only. CLI commands, exit codes, and eval rules match 0.2.0.

Changes

• Version 0.2.1 in pyproject.toml, src/jevcheck/__init__.py, the Action input jevcheck-version (default), and tests/test_cli.py.
• SPDX license metadata: license = "MIT", license-files = ["LICENSE"]. Removed the deprecated License :: OSI Approved :: MIT License classifier. Build backend requires setuptools>=77.
• Python 3.13 and 3.14 in classifiers and the ci.yml test matrix. requires-python stays >=3.11. 3.11 and 3.12 stay in the matrix.
• project.urls: Homepage, Source, Documentation, Issues, Changelog.
• CHANGELOG.md (Keep a Changelog) for 0.1.0, 0.2.0, and 0.2.1 from git history and the existing tags. MANIFEST.in includes CHANGELOG.md and RELEASING.md.
• README install leads with pip install jevcheck. The editable install stays under Develop. In-repo README links are absolute GitHub URLs so they resolve on PyPI.
• Action refs in README.md, docs/tutorial.md, examples/README.md, and examples/jevcheck.yml pin @v0.2.1 instead of @main. v0.2.0 does not contain .github/actions/jevcheck.

There is no publish workflow. .github/workflows/ is ci.yml, jevcheck-example.yml, pr-triage.yml, and plugin-scan.yml.

jevcheck-example.yml uses the composite action, which installs jevcheck==0.2.1 from PyPI. That job stays red until the post-merge upload. ci.yml installs the checkout and does not need PyPI.

Verification

TYPESAFE_API_KEY was unset. tests/test_live.py skipped. No live API calls.

Python	Result
3.11.16	124 passed, 1 skipped
3.13.15	124 passed, 1 skipped
3.14.7	124 passed, 1 skipped

Skip: tests/test_live.py:15 — TYPESAFE_API_KEY not set; live System One call skipped.

python -m build (isolated env, setuptools 84.0.0, wheel 0.48.0) produced jevcheck-0.2.1-py3-none-any.whl and jevcheck-0.2.1.tar.gz. Wheel metadata:

• Metadata-Version: 2.4
• Version: 0.2.1
• License-Expression: MIT
• License-File: LICENSE
• Classifiers include Python 3.11–3.14 and do not include a License classifier
• Project URLs: Homepage, Source, Documentation, Issues, Changelog

twine 7.0.0 / build 1.6.1:

Checking jevcheck-0.2.1-py3-none-any.whl: PASSED
Checking jevcheck-0.2.1.tar.gz: PASSED

twine check --strict also PASSED. The build log has no setuptools license deprecation warnings. It still prints the existing MANIFEST.in notices no previously-included files matching ... for __pycache__, *.py[cod], and .env.

Post-merge steps

Full copy-paste notes are in RELEASING.md. Short form:

1. Merge this PR. Tag that merge commit (not this branch tip) and push the tag:

   git switch main
   git pull origin main
   git tag -a v0.2.1 -m "v0.2.1 — GitHub Action, tutorial, and packaging metadata"
   git push origin v0.2.1

2. Create the GitHub Release from that tag. Title: v0.2.1 — GitHub Action, tutorial, and packaging metadata. Body: the notes in RELEASING.md under "GitHub release notes for v0.2.1". Install is pip install jevcheck==0.2.1, with no "after PyPI publish" heading.

3. From a clean checkout of v0.2.1:

   git switch --detach v0.2.1
   python3 -m venv .venv-release
   source .venv-release/bin/activate
   python -m pip install --upgrade build twine
   python -m build
   python -m twine check dist/*
   python -m twine upload dist/*

The existing v0.2.0 release still says "Install (after PyPI publish)" even though PyPI has had jevcheck==0.2.0 since 2026-09-19. This PR cannot edit that release. If you edit it by hand, replace that section with:

## Install

```
pip install jevcheck==0.2.0
```

Leave the v0.2.0 tag where it is. If the 0.2.1 tag date is not 2026-09-30, update the [0.2.1] heading in CHANGELOG.md.