docs for the constraints file to support this request: https://pip.pypa.io/en/stable/user_guide/#constraints-files

Mind testing the implementation in #225 @ commit 6423874?

You'll need to use the following GHA workflow configuration:

uses: py-actions/py-dependency-install@642387473628e92c4b9ac198b5ba51b9102d3f08

If you use a custom requirements.txt path, the input field name changed to requirements-path. You can now define a constraints file with the input field name: constraints-path. In the current implementation, constraints files are an off by default option that must be explicitly defined with a path to a constraints file. Requirements file installs remain in use by default and defined at requirements.txt by default.

Let me know if that works for you. If that does the trick, I'll update the docs, merge, and cut a new major release (the path to requirements-path change is backwards incompatible).

Ty!

Still haven't received feedback here to confirm that this addresses the issue. Can anyone confirm so that we can land this if it is important to anyone out there?

@chrissimpkins I made some notes on your PR. I don't use the action personally, but some projects I contribute to, do. So they'll get the update upon release. In general, what you did will work. Though, with my suggestions, the things will go smoother. Especially, the recommendation to use the env var, which is going to be even more useful as we've merged a PR in pip-tools that allows generating constraints for PEP 517 build deps.