* For stability provide the commit SHA that corresponds to the 0.5.0
  tag for users to pin to.

…74)

* To guard against invalid dates being viewed as being older than the
  removal threshold date first check that the upload date is YYYY-MM-DD
  formatted. If not, warn in the logs and skip the offending package.

Bumps the actions group with 1 update: [peaceiris/actions-gh-pages](https://github.com/peaceiris/actions-gh-pages).


Updates `peaceiris/actions-gh-pages` from 3.9.3 to 4.0.0
- [Release notes](https://github.com/peaceiris/actions-gh-pages/releases)
- [Changelog](https://github.com/peaceiris/actions-gh-pages/blob/main/CHANGELOG.md)
- [Commits](peaceiris/actions-gh-pages@373f7f2...4f9cc66)

---
updated-dependencies:
- dependency-name: peaceiris/actions-gh-pages
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <[email protected]>

* Use full commit SHAs for all GitHub actions as described in SPEC 8.

Bumps the actions group with 1 update: [actions/checkout](https://github.com/actions/checkout).


Updates `actions/checkout` from 4.1.6 to 4.1.7
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@a5ac7e5...692973e)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps the actions group with 1 update: [actions/setup-python](https://github.com/actions/setup-python).


Updates `actions/setup-python` from 5.1.0 to 5.1.1
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@82c7e63...39cd149)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Users of the action should generate an access token from their
  own Anaconda Cloud account, not from the Scientific Python organisation's
  account.

Bumps the actions group with 1 update: [actions/setup-python](https://github.com/actions/setup-python).


Updates `actions/setup-python` from 5.1.1 to 5.2.0
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@39cd149...f677139)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* As the test project does not need any part of setuptools specific
  infrastructure, use hatchling as the build backend.

* ENH: Use pixi to run action as composite

* Use pixi to manage the environment fully, which removes the needs for
  micromamba and a Linux container, allowing the action to be run as a
  'composite' action.
   - This allows the action to be used on macOS runners in addition
     to Linux.
   - Add pixi project configuration and pixi lock file.
   - Add 'osx-64' and 'osx-arm64' platforms to pixi environment solves
     to allow for use on Linux and macOS runners.
   - Use prefix-dev/setup-pixi GitHub action to setup pixi for the action.
   - Explicitly enable the 'locked' option for prefix-dev/setup-pixi.
   - Don't allow for post job cleanup to avoid errors if the action is
     run multiple times in a workflow (this is a downside of no longer
     being in a Linux container).
   - Note: GitHub Actions takes care of cleaning up the environment after
     each run, so you are not responsible for manually unsetting all
     environment variables between steps to avoid secret leakage.
   - Make cmd.sh executable (chmod +x).
* Remove use of micromamba in the upload script.
* Remove the conda-lock files and the Docker based locking workflow.
* Remove Dockerfile.
* Note in the README that the runner used can be either Linux or macOS.
* Update version numbers of action to v0.5.0.

* MNT: Rename script to 'upload_wheels.sh'

* As the script is no longer the CMD of a Linux container but is now a
  standalone Bash script, having a more descriptive name is preferable.

* Update project version metadata from v0.5.0 to v0.6.0.