Bump conda-incubator/setup-miniconda from 2 to 3#12260
Conversation
Bumps [conda-incubator/setup-miniconda](https://github.com/conda-incubator/setup-miniconda) from 2 to 3. - [Release notes](https://github.com/conda-incubator/setup-miniconda/releases) - [Changelog](https://github.com/conda-incubator/setup-miniconda/blob/main/CHANGELOG.md) - [Commits](conda-incubator/setup-miniconda@v2...v3) --- updated-dependencies: - dependency-name: conda-incubator/setup-miniconda dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
Doc builds would have failed until fatiando/pooch#379 is resolved, but given how deep in our code these |
| Can be "auto", "light", or "dark" or a path-like to a | ||
| custom stylesheet. For Dark-Mode and automatic Dark-Mode-Detection, | ||
| :mod:`qdarkstyle` and | ||
| `qdarkstyle <https://github.com/ColinDuquesnoy/QDarkStyleSheet>`__ and |
There was a problem hiding this comment.
I can see the argument for dropping niche dependencies from intersphinx, but FWIW I also worry that hard-coded URLs like this will need to change eventually (eg. if QDarkStyleSheet repo ownership is transferred to an org or whatever). I guess it's a question of how frequent the annoyance is likely to be.
There was a problem hiding this comment.
FWIW I also worry that hard-coded URLs like this will need to change eventually
We have the same issue with intersphinx URLs, too -- people can change where their docs are hosted, and that does happen from time to time. At least when repos are moved, GitHub mirrors / redirects repo moves to the new location I think. So hopefully this is actually an improvement in that regard! And we have monthly linkcheck to check it for us which is probably good enough.
3b9676b to
b2ced04
Compare
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Eric Larson <larson.eric.d@gmail.com>
Bumps conda-incubator/setup-miniconda from 2 to 3.
Release notes
Sourced from conda-incubator/setup-miniconda's releases.
... (truncated)
Changelog
Sourced from conda-incubator/setup-miniconda's changelog.
... (truncated)
Commits
11b5629Prepare 3.0.1 (#326)8706aa7Fix env activation on win (a v3 regression) due to hard-coded install PATH (#...c585a97Bump conda-incubator/setup-miniconda from 2.3.0 to 3.0.0 (#321)2defc80Prepare release (#320)0d5a56bBump actions/checkout from 2 to 4 (#319)45fd3f9Merge pull request #316 from dbast/timeoutd1e04fcMerge pull request #299 from isuruf/condaBasePathfab0073Merge pull request #318 from dbast/readmefa6bdf9Update with npm run buildd42f8b8Fix condaBasePath when useBundled is false, and there's no pre-existing condaDependabot 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)