Having a “universal” lock file will cause version conflicts for big projects. The more workflows the higher the chance of hitting this problem. I'd like to request a way to point a workflow to a different lock file so that it'd be possible to have multiple lock files committed and maintained separately.
This would also allow testing against different sets of dependencies deliberately (one known case is all the known lowest supported versions of actions your automation depends on).
Having a “universal” lock file will cause version conflicts for big projects. The more workflows the higher the chance of hitting this problem. I'd like to request a way to point a workflow to a different lock file so that it'd be possible to have multiple lock files committed and maintained separately.
This would also allow testing against different sets of dependencies deliberately (one known case is all the known lowest supported versions of actions your automation depends on).