Bump mamba-org/provision-with-micromamba from 15 to 16#1766
Bump mamba-org/provision-with-micromamba from 15 to 16#1766dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [mamba-org/provision-with-micromamba](https://github.com/mamba-org/provision-with-micromamba) from 15 to 16. - [Release notes](https://github.com/mamba-org/provision-with-micromamba/releases) - [Commits](mamba-org/provision-with-micromamba@v15...v16) --- updated-dependencies: - dependency-name: mamba-org/provision-with-micromamba dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
We'll need to take action to switch to another package... |
We can enable pre-commit CI but I'm not sure I ever inherited enough rights to do that. Only @wrobstory can do it. |
|
Is that necessary? In the release notes it says: See the migration guide for instructions how to migrate from provision-with-micromamba to setup-micromamba. So I guess that means we have to switch the GitHub actions config to use a different thing |
I meant the GHA for pre-commits. Not micromamba. This PR is fine to be merged but the pre-commit one will keep failing b/c upstream is no longer supporting it.
I would just delete the pre-commit GHA and enable pre-commit-ci, which only @wrobstory can do, but the rest should remain as-is IMO. |
|
I'm not following you. This bot PR has nothing to do with pre-commit hasn't it? It's about the micromamba action we're using being deprecated. I opened a PR that uses the recommended replacement action and it seems to be all working: #1767 Whether we want to switch to precommit.ci is something else. https://github.com/pre-commit/action says they are in maintenance-only, so that sounds fine to me. As long as it keeps working, we don't need new features. I'd rather not switch to an external CI only to have them drop the free option once everyone moved over. I propose we close this one and merge #1767 |
Yes and no. It will update all GHA. B/c the pre-commit ones were the only tests failing I thought you meant that one.
Besides the pre-commit GHA. The rest is fine and you don't need a new PR for that. You can just merge this one. The intermittent fail on the pre-commit will continue though. Also, that one won't get updates b/c it is deprecate it lieu of pre-commit-ci.
Sure. This one or the other. Both update the micromamba GHA. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps mamba-org/provision-with-micromamba from 15 to 16.
Release notes
Sourced from mamba-org/provision-with-micromamba's releases.
Commits
3c96c0cAdd deprecation warning (#122)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)