Bump django-vectortiles from 0.2.0 to 1.0.0 in /src

[dependabot]

Bumps django-vectortiles from 0.2.0 to 1.0.0.

Release notes

Sourced from django-vectortiles's releases.

1.0.0

What's Changed

• ✨ Implement native rest_framework renderer (thanks StefanBrand) by @​submarcos in submarcos/django-vectortiles#32
• Improve code quality and documentation by @​submarcos in submarcos/django-vectortiles#34
• Drop django 2.2 and python 3.6, add django 4.2 and python 3.11 by @​submarcos in submarcos/django-vectortiles#39
• PostGIS backend uses connection the DB provided by get_queryset. by @​kxtells in submarcos/django-vectortiles#40
• Support psycopg3 by @​submarcos in submarcos/django-vectortiles#42
• Improve v1 by @​submarcos in submarcos/django-vectortiles#46
• Bump actions/checkout from 3 to 4 by @​dependabot in submarcos/django-vectortiles#45
• Bump actions/setup-python from 4 to 5 by @​dependabot in submarcos/django-vectortiles#47
• v1 by @​submarcos in submarcos/django-vectortiles#35
• Improve readme and doc by @​submarcos in submarcos/django-vectortiles#49
• Drop django 3.2 and add 5.1, add python 3.12 by @​submarcos in submarcos/django-vectortiles#50

New Contributors

• @​kxtells made their first contribution in submarcos/django-vectortiles#40
• @​dependabot made their first contribution in submarcos/django-vectortiles#45

Full Changelog: submarcos/django-vectortiles@0.2.0...1.0.0

1.0.0-beta3

What's Changed

• ✨ Implement native rest_framework renderer (thanks StefanBrand) by @​submarcos in submarcos/django-vectortiles#32
• Improve code quality and documentation by @​submarcos in submarcos/django-vectortiles#34
• Drop django 2.2 and python 3.6, add django 4.2 and python 3.11 by @​submarcos in submarcos/django-vectortiles#39
• PostGIS backend uses connection the DB provided by get_queryset. by @​kxtells in submarcos/django-vectortiles#40

New Contributors

• @​kxtells made their first contribution in submarcos/django-vectortiles#40

1.0.0-beta2

What's Changed

• Move mapbox subdepencies to python (native implementation) pip install django-vectortiles[python]
• Refactor classes and method names to get possibility to define multiple vector layer by tile / view
• PostGIS or Python backend is now defined in setting
• Add real complex example in test project
• ✨ Implement native rest_framework renderer (thanks StefanBrand) by @​submarcos in submarcos/django-vectortiles#32
• Improve code quality and documentation by @​submarcos in submarcos/django-vectortiles#34
• Drop django 2.2 and python 3.6, add django 4.2 and python 3.11 by @​submarcos in submarcos/django-vectortiles#39

Full Changelog: submarcos/django-vectortiles@0.2.0...1.0.0-beta2

1.0.0-beta1

What's Changed

• Move mapbox subdepencies to python (native implementation) pip install django-vectortiles[python]
• Refactor classes and method names to get possibility to define multiple vector layer by tile / view
• PostGIS or Python backend is now defined in setting
• Add real complex example in test project

... (truncated)

Changelog

Sourced from django-vectortiles's changelog.

1.0.0 (2024-09-04)

Breaking changes

• Refactor PostGIS and Python (old named MapBox) backends usage. Use setting to set (default postgis)
• No DetailView anymore. As Tile can have many layers, declare VectorLayer on MVTView (one or many).

Enhancements

• Add compatibility to use with psycopg v3

• Drop python 3.6 and Django 2.2, 3.2

• Add python 3.11, 3.12 and Django 4.2, 5.0, 5.1

• Features

  • Native MVTRenderer for django-rest-framework

• Quality

  • Black-ified
  • iSort-ed

• Documentation

  • Add DRF and MapLibre examples

Commits

• 5b9e818 prepare release
• 8fc9fc5 Merge pull request #50 from submarcos/drop_3.2_add_5.1
• 05714f5 drop django 3.2 and add 5.1 in CI
• c1d66d8 drop django 3.2 and add 5.1 in CI
• a9e5fd5 drop django 3.2 and add 5.1 in CI
• 6e73ca7 drop django 3.2 and add 5.1 in CI
• 9ac457d drop django 3.2 and add 5.1 in CI
• 2a8f9c4 Merge pull request #49 from submarcos/improve_readme_and_doc
• 8a0109f Apply suggestions from code review
• 9e1e837 improve doc
• 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)