Skip to content
Discussion options

You must be logged in to vote

The package is maintained and no longer lags. Releases now build the wheel and the Docker images as parallel jobs in a single workflow from the same commit and version, and a missing PyPI publish raises a warning on the release rather than passing silently. PyPI currently serves 0.45.0, matching the repository, and every release from 0.40.0 onwards is present; the gap you ran into in 2025 was a publishing outage that has since been fixed. So installing from PyPI and pinning a version is a reasonable way to keep upgrading without forking. The caveat is that there is no declared public Python API: the package exports nothing from its root, the only supported entry point is the pr-agent cons…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by IsmaelMartinez
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants