Releases

Pupa the app and pupa-backend ship separately and neither one pins the other: the backend reports its version from GET /auth/config, and the app uses that for its own checks. There is no published compatibility table.

So the version shown against a release is not a declared guarantee. It is the newest pupa-backend on PyPI at the moment that release was published, which is the build that release was developed and tested against. In practice, running the latest backend is the right answer.