Action failing due to missing pixi.lock

[trallard]

Hey there, we recently bumped the upload-nightly-action to v6 in PyData Sphinx theme, though since doing so, this keeps failing on CI
with the following error:

Error: Failed to generate cache key: Error: ENOENT: no such file or directory, open 'pixi.lock'
    at /home/runner/work/_actions/prefix-dev/setup-pixi/ba3bb36eb2066252b2363392b7739741bb777659/dist/index.js:80915:9

It seems this is now expecting the project to have a Pixi.lock file, I am assuming this is coming from

upload-nightly-action/action.yml

Line 32 in ccf29c8

locked: true

But this is not documented in the README, so I am not entirely sure. We do not use pixi, so what would then be the alternative? Would it be possible to expose the locked option so that the user can set to false in such cases?

[matthewfeickert]

@trallard v0.6.0 had a bug so please bump to v0.6.1. Depending on your Dependabot frequency you can either wait for it or use the version listed in the current README.

upload-nightly-action/README.md

Lines 11 to 18 in 920fb59

	jobs:
	steps:
	...
	- name: Upload wheel
	uses: scientific-python/upload-nightly-action@82396a2ed4269ba06c6b2988bb4fd568ef3c3d6b # 0.6.1
	with:
	artifacts_path: dist
	anaconda_nightly_upload_token: ${{secrets.UPLOAD_TOKEN}}

The projects using the uploader are not required to use pixi, we had a path resolver issue in the action not caught by local testing that was resolved with v0.6.1 thanks to @MridulS.

(Apologies for typos. I'm responding on phone.)

[matthewfeickert]

I've gone through every project currently listed in #30 (comment) and verified that they either aren't using the action or were on the "right" side of the Dependabot schedule to get the v0.6.1 update. If they were on v0.6.0 I've opened a PR to fix.

Note to future self: Having projects use Depenabot to manage their GitHub Actions helps a lot in being able to quickly diagnose if people are affected by bugs in releases or not. 👍