Update scikit-image requirement from <0.20,>=0.17.2 to >=0.17.2,<0.21

[dependabot]

Updates the requirements on scikit-image to permit the latest version.

Changelog

Sourced from scikit-image's changelog.

How to make a new release of skimage

While following this guide, note down all the times that you need to consult a previous release manager, or that you find an instruction unclear. You will, of course, make a PR to update these notes after you are done with the release! ;-)

Before you start, make sure you have all the required write permissions (if not, you will need to ask an owner to grant you access), specifically to:

• https://pypi.org/project/scikit-image/

• https://github.com/scikit-image/scikit-image-web

• Check TODO.txt for any outstanding tasks.

We use a variant of "semantic versioning", where version numbers are classified as v... By default, releases are made from the main branch as part of a linear release history and, as described below, are triggered by pushing a git tag to the scikit-image repository on github. If a patch release is required for an older version, a branch can be created from the appropriate point in main and the following instructions are still apt.

• Update the release notes (note this will soon change with the addition of Towncrier integrated directly into the CI):

  1. Review and cleanup doc/release/release_dev.rst.

  2. Make a list of merges, contributors, and reviewers by running tools/generate_release_notes.py -h and following that file's usage.

  3. Paste this list at the end of the release_dev.txt.

  4. Scan the PR titles for highlights, deprecations, API changes, and bugfixes, and mention these in the relevant sections of the notes. Try to present the information in an expressive way by mentioning the affected functions, elaborating on the changes and their consequences. If possible, organize semantically close PRs in groups.

  5. Check for duplicate names in the automatically generated list of contributors and reviewers

  6. Rename the file to doc/release/release_<major>.<minor>.txt

  7. Copy doc/release/release_template.txt to doc/release/release_dev.txt for the next release.

  8. Copy relevant deprecations from release_<major>_<minor>.txt

... (truncated)

Commits

• 5e74a4a Designate 0.20.0 release
• 0d09ff1 Merge pull request #6766 from jarrodmillman/release-notes-0.20.0
• 1895495 Re-add missing sections and update style
• 2571da1 Edit release notes summary
• 38b0849 Add recently merged PR 6768
• 6182c93 Update author section
• 6655762 Hide PRs that were backported to 0.19.x
• b13988e Finish sorting new PRs into categories
• a2289f6 Continue sorting new PRs into categories
• 0bd0ca4 Remove duplicate classifier in pyproject.toml
• Additional commits viewable in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codecov]

Codecov Report

Merging #882 (acbdabb) into master (58eaa34) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #882   +/-   ##
=======================================
  Coverage   85.30%   85.30%           
=======================================
  Files          74       74           
  Lines        8774     8774           
=======================================
  Hits         7485     7485           
  Misses       1289     1289           

Flag	Coverage Δ
macos-latest-3.10	?
ubuntu-latest-3.10	85.17% <ø> (ø)
ubuntu-latest-3.7	85.07% <ø> (ø)
ubuntu-latest-3.8	85.19% <ø> (ø)
ubuntu-latest-3.9	85.19% <ø> (ø)
windows-latest-3.9	?

Flags with carried forward coverage won't be shown. Click here to find out more.