build(deps): bump icalendar from 5.0.12 to 6.0.0

[dependabot[bot]]

Bumps icalendar from 5.0.12 to 6.0.0.

Release notes

Sourced from icalendar's releases.

v6.0.0

To view the changes, please see the Changelog. This release can be installed from PyPI.

v6.0.0a0

To view the changes, please see the Changelog. This release can be installed from PyPI.

v5.0.13

No release notes provided.

Changelog

Sourced from icalendar's changelog.

6.0.0 (2024-09-28)

Minor changes:

• Add __all__ variable to each modules in icalendar package
• Improve test coverage.
• Adapt test_with_doctest.py to correctly run on Windows.
• Measure branch coverage when running tests.
• Export Component base class for typing

New features:

• Use pyproject.toml file instead of setup.py

Bug fixes:

• Fix link to stable release of tox in documentation.
• Fix a bad bytes replace in unescape_char.
• Handle ValueError in vBinary.from_ical.
• Ignore the BOM character in incorrectly encoded ics files.

6.0.0a0 (2024-07-03)

Minor changes:

• Test that all code works with both pytz and zoneinfo.
• Add message to GitHub release, pointing to the changelog
• Make coverage report submission optional for pull requests
• Parallelize coverage
• Rename master branch to main, see Issue <https://github.com/collective/icalendar/issues/627>_
• Update docs/usage.rst to use zoneinfo instead of pytz.
• Added missing public classes and functions to API documentation.
• Improved namespace management in the icalendar directory.
• Add Python version badge and badge for test coverage
• Remove 4.x badge
• Update list of tox environments
• Use Coveralls' GitHub Action
• Check distribution in CI

Breaking changes:

• Use zoneinfo for icalendar objects created from strings, see Issue [#609](https://github.com/collective/icalendar/issues/609) <https://github.com/collective/icalendar/issues/609>_.

  This is an tested extension of the functionality, not a restriction: If you create icalendar objects with pytz timezones in your code, icalendar will continue to work in the same way.

... (truncated)

Commits

• 37c522b Merge pull request #710 from niccokunzmann/release
• 354a6e0 update maintenance to v6
• 0f210f8 Fix install.rst again
• e48dcfb Fix the doctests
• 2f47800 correct install.rst
• 443519c alpha -> stable
• 4673e04 remove the version update as this is now done by tags
• 17dba94 Update changes for release
• ca260c8 Merge pull request #707 from niccokunzmann/issue-686-pyproject.toml
• cc4635f Document outdated email
• 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)