Bump timezonefinder from 6.5.9 to 7.0.1

[dependabot]

Bumps timezonefinder from 6.5.9 to 7.0.1.

Changelog

Sourced from timezonefinder's changelog.

7.0.1 (2025-07-24)

• hit PyPI project size limit. triggering re-upload to fix missing sdist in 7.0.0 release.
• deleted all PyPI releases up to version 3.4.2 (last version supporting python 2.7) to free up project space

7.0.0 (2025-07-21)

• Simplified API for end-users, reducing redundant code

• Added global functions that use a shared TimezoneFinder instance:

  • timezone_at
  • timezone_at_land
  • unique_timezone_at
  • certain_timezone_at
  • get_geometry

• Documented usage and warned about thread safety considerations for global functions

• Updated command line interface to use global functions where appropriate

• breaking API Changes: clarified naming. renamed "boundary" to "bbox". renamed "polygon" to "boundary". boundaries (the outer polygon defining part of a timezone) and holes are both polygons so hence the name "polygon" is ambiguous.

6.6.3 (2025-07-21)

• when in_memory=True, all polygon numpy arrays are constructed once during startup rather than repeatedly on demand. This should significantly improve performance for applications that make frequent polygons queries.
• Created a coord_accessors.py module for abstracting access to polygon coordinates, allowing for both in-memory and file-based access.
• added auto-generated data report to the documentation. thanks to ARYAN RAJ <https://github.com/nikkhilaaryan>__ for the PR.

6.6.2 (2025-07-19)

• hotfix missing hole_registry.json in the distributions
• added integration tests in CI/CD. Thanks to theirix <https://github.com/theirix>__

6.6.1 (2025-07-18)

• hotfix missing flatbuf module in the distributions
• added tests for checking the content of the distributions

6.6.0 (2025-07-17)

... (truncated)

Commits

• e18a5f5 7.0.1 reupload missing sdist (#322)
• 6bb1f34 update documentation (#316)
• a8f9c40 297 ux reuse global timezonefinder instance (#315)
• 6a4a8d6 309 optimisation construct numpy arrays in memory mode (#314)
• bd61947 Add data report (#305)
• 3af520e Add end-to-end test to verify wheels (#310)
• 2464cbd add missing hole_registry.json (#308)
• 80e7219 Fix missing protobof package in dist (#304)
• c9f06b5 Bugfix pypi deployment (#302)
• 84b19e9 Binary polygon data structure refactoring (#287)
• 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)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}