Bump webcolors from 1.11.1 to 24.8.0

[dependabot]

Bumps webcolors from 1.11.1 to 24.8.0.

Changelog

Sourced from webcolors's changelog.

.. _changelog:

Changelog

This document lists the changes in each release of webcolors.

Version numbering

This library currently tracks its version numbers using the YY.MM.MICRO form of Calendar Versioning <https://calver.org>_ ("CalVer"), in which the first two components of the version number are the (two-digit) year and (non-zero-padded) month of the release date, while the third component is an incrementing value for releases occurring in that month. For example, the first release issued in January 2025 would have a version number of 25.1.0; a subsequent release in the same month would be 25.1.1; a release the following month (February) would be 25.2.0.

The CalVer system was adopted for this library in 2024, and the first release to use a CalVer version number was 24.6.0.

API stability and deprecations

The API stability/deprecation policy for this library is as follows:

• The supported stable public API of this library is the set of symbols which are exported by its __all__ declaration and which are documented in this documentation. For classes exported there, the supported stable public API is the set of methods and attributes of those classes whose names do not begin with one or more underscore (_) characters and which are documented in this documentation.

• When a public API is to be removed, or undergo a backwards-incompatible change, it will emit a deprecation warning which serves as notice of the intended removal or change, and which will give a date -- which will always be at least in the next calendar year after the first release which emits the deprecation warning -- past which the removal or change may occur without further warning.

• Security fixes, and fixes for high-severity bugs (such as those which might cause unrecoverable crash or data loss), are not required to emit deprecation warnings, and may -- if needed -- impose backwards-incompatible change in any release. If this occurs, this changelog document will contain a note explaining why the usual deprecation process could not be followed for that case.

... (truncated)

Commits

• ec0702e Release 24.8.0.
• a9a668a Fix reST formatting in testing docs.
• dee9d46 Add first draft of names() function (refs #20).
• bb87686 Release 24.6.0.
• 41046b0 Reorganize and update the FAQ.
• 0f865b2 Slight clarification in testing docs.
• 368e2c5 Minor word-order change for version references in docs.
• 516e863 Small modernization of Python idioms.
• 68ba427 Be absolutely clear about the mappings no longer being supported API.
• 785d6da Update the code comment on gray/grey choices.
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[Dreamsorcerer]

The checkout step is failing on these 2 dependabot PRs. Never seen that before...

[Dreamsorcerer]

@dependabot recreate

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.70%. Comparing base (b4092d9) to head (1c61425).
Report is 592 commits behind head on 3.11.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             3.11    #8865   +/-   ##
=======================================
  Coverage   97.70%   97.70%           
=======================================
  Files         108      108           
  Lines       34198    34198           
  Branches     4064     4064           
=======================================
  Hits        33413    33413           
  Misses        586      586           
  Partials      199      199           

Flag	Coverage Δ
CI-GHA	97.60% <ø> (ø)
OS-Linux	97.28% <ø> (+<0.01%)	⬆️
OS-Windows	94.82% <ø> (ø)
OS-macOS	96.96% <ø> (ø)
Py-3.10.11	97.05% <ø> (ø)
Py-3.10.14	96.98% <ø> (ø)
Py-3.11.9	97.22% <ø> (ø)
Py-3.12.4	94.63% <ø> (ø)
Py-3.12.5	97.02% <ø> (+<0.01%)	⬆️
Py-3.9.13	96.95% <ø> (ø)
Py-3.9.19	96.89% <ø> (ø)
Py-pypy7.3.16	96.49% <ø> (ø)
VM-macos	96.96% <ø> (ø)
VM-ubuntu	97.28% <ø> (+<0.01%)	⬆️
VM-windows	94.82% <ø> (ø)

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.