Remove pinned micromamba version from workflow files
This PR removes all occurrences of the micromamba-version: "1.5.10-0" specification from GitHub workflow files, as the underlying issue that necessitated this pin has been resolved.
Background
The micromamba version was previously pinned to 1.5.10-0 as a workaround for https://github.com/mamba-org/setup-micromamba/issues/225. Now that this issue has been resolved, we can remove the version pin and use the default version provided by the mamba-org/setup-micromamba action.
Changes
Removed micromamba-version: "1.5.10-0" from:
.github/workflows/mypy.yml.github/copilot-setup-steps.yml.github/workflows/test.yml(2 occurrences)
The workflows will now automatically use the latest compatible version of micromamba provided by the setup-micromamba action, ensuring we benefit from bug fixes and improvements without manual version updates.
Testing
The changes only affect CI/CD workflow configuration. The workflows will be tested automatically when this PR is merged, using the default micromamba version provided by the action.
Original prompt
Remove all occurrences of the line 'micromamba-version: "1.5.10-0"' from workflow files in the pymc-devs/pytensor repository. This includes:
- .github/workflows/mypy.yml
- .github/copilot-setup-steps.yml
- .github/workflows/test.yml This line was present due to https://github.com/mamba-org/setup-micromamba/issues/225, which is now resolved. The workflows should now use the default version of micromamba provided by the action. Make sure to remove this line everywhere it appears in the above files and do not alter anything else.
References:
- https://github.com/pymc-devs/pytensor/blob/main/.github/workflows/mypy.yml
- https://github.com/pymc-devs/pytensor/blob/main/.github/copilot-setup-steps.yml
- https://github.com/pymc-devs/pytensor/blob/main/.github/workflows/test.yml
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
Muahahaha!!! It's modifying itself!!! :robot: :robot: :robot: :robot:
Hmm, the breakage may have been preexisting, revealed only now due to micromamba cache busting. Will try to have a look tomorrow.
btw I don't think the setup actually ran (I don't see it in any actions or in the logs), so it may indeed be that it must go inside "workflows" like other CI jobs.