assert-python

Composite action for Forgejo Actions. It fails at the setup boundary if setup-python left a different interpreter active. Requires Bash and python on the job runner; it neither installs Python nor caches dependencies.

Usage

steps:
  - uses: https://code.forgejo.org/actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97
    with:
      python-version: '3.14'
  - uses: https://git.vexly.cc/actions/assert-python@c5098e5d5a97b074df8c06d31f917a922e971bf8
    with:
      version: '3.14'

The example pins release v0.1.0 to its reviewed full commit SHA. The action's version input accepts major.minor; malformed input exits 2, a mismatch exits 1, and an exact match exits 0. No checkout of the consumer repository is needed: the script is loaded from github.action_path.

To verify locally, run python -m unittest discover -s tests -v in this directory. In the consumer repository, verify both match and mismatch on a real Forgejo runner before changing required checks.

The published action passed matching/mismatching interpreter checks on Forgejo 16.0.5 / Runner 13.0.0 in TokenSell and an independent consumer. Both probes load the action without checking out TokenSell.