Unpin protobuf sub-dependency (mapbox_vector_tiles fixed)

[submarcos]

No description provided.

[codecov]

Codecov Report

Base: 100.00% // Head: 100.00% // No change to project coverage 👍

Coverage data is based on head (1bf7ddd) compared to base (5739b42).
Patch has no changes to coverable lines.

Additional details and impacted files

@@            Coverage Diff             @@
##            master       #33    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files           12         9     -3     
  Lines          279       164   -115     
==========================================
- Hits           279       164   -115     

Impacted Files	Coverage Δ
vectortiles/mixins.py	100.00% <0.00%> (ø)
vectortiles/postgis/functions.py	100.00% <0.00%> (ø)
vectortiles/tests/test_mixins.py
vectortiles/tests/test_functions.py
vectortiles/tests/test_views.py

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
371130	Assigned	Django Secret Key	8830af0	test_vectortiles/settings/init.py	View secret
5635927	Triggered	Generic Password	8830af0	.github/workflows/python-test.yml	View secret
5635927	Triggered	Generic Password	8830af0	.github/workflows/python-test.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}