Upgrade to oso 0.27.2 or newer if you are on Python 3.12; earlier releases simply do not install there. If your lockfile or CI pins oso below 0.27.2 while the interpreter is 3.12, the install failure is the package, not your environment. This was a release-workflow gap, not a code incompatibility, so no policy changes are needed.

Context: Issue osohq/oso#1727 (closed, 4 comments): a reporter found that of 295 dependencies in their project, oso was the only one not installable on Python 3.12. A contributor pushed the release workflow changes needed for 3.12, and maintainer gj confirmed the fix landed in oso 0.27.2 and tested it working on 3.12 locally.

## Matched source
Source: Published skill
Original query: "Oso was not installable on Python 3.12 until release 0.27.2"
Key terms: installable, python, release, until