Hey folks, I decided to move my release steps into dedicated jobs in order to deploy to separate environments, and as such noticed pnpm is no longer able to detect my package.json since the cwd is the current repo
[release](https://github.com/josefaidt/fakerepo/runs/7584874320?check_suite_focus=true#step:2:17)
Error: ENOENT: no such file or directory, open '/home/runner/work/fakerepo/fakerepo/package.json'
is there a way to detect the repo name in order to prevent duplicating it in the detected path? or can we manually re-point the package.json path?
for example, here is a snippet from the release flow where we're calling a reusable release-env action
Hey folks, I decided to move my release steps into dedicated jobs in order to deploy to separate environments, and as such noticed pnpm is no longer able to detect my package.json since the cwd is the current repo
is there a way to detect the repo name in order to prevent duplicating it in the detected path? or can we manually re-point the package.json path?
for example, here is a snippet from the release flow where we're calling a reusable
release-env
action