Update dependency mapbox-gl to v1.13.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
mapbox-gl	1.12.0 -> 1.13.3
@types/mapbox-gl (source)	1.12.5 -> 1.13.10

---

Release Notes

mapbox/mapbox-gl-js (mapbox-gl)

v1.13.3

Compare Source

🐞 Bug fixes

• Fix incorrect billing when customAccessToken is provided along with non-Mapbox tiles (#​12520)
• Prevent video sources from entering fullscreen on iOS Safari (#​11067)
• Upgrade minimist to ^1.2.7 to avoid CVE-2021-44906 (#​12442) (h/t @​Spasfonx)

v1.13.2

Compare Source

🐞 Bug fixes

• Backports a fix for an iOS 15 issue where the iOS Safari tab bar interrupts touch interactions. (#​11084)

v1.13.1

Compare Source

1.13.1

🐞 Bug fixes

• Fix ImageSource not working in some cases in Firefox & Safari. #​10230

v1.13.0

Compare Source

✨ Features and improvements

• Improve accessibility by fixing issues reported by WCAG 2.1. #​9991
• Improve accessibility when opening a popup by immediately focusing on the content. #​9774 (h/t @​watofundefined)
• Improve rendering performance of symbols with symbol-sort-key. #​9751 (h/t @​osvodef)
• Add Marker clickTolerance option. #​9640 (h/t @​ChristopherChudzicki)
• Add Map hasControl method. #​10035
• Add Popup setOffset method. #​9946 (h/t @​jutaz)
• Add KeyboardHandler disableRotation and enableRotation methods. #​10072 (h/t @​jmbott)

🐞 Bug fixes

• Fix a bug where queryRenderedFeatures didn't properly expose the paint values if they were data-driven. #​10074 (h/t @​osvodef)
• Fix a bug where attribution didn't update when layer visibility changed during zooming. #​9943
• Fix a bug where hash control conflicted with external history manipulation (e.g. in single-page apps). #​9960 (h/t @​raegen)
• Fix a bug where fitBounds had an unexpected result with non-zero bearing and uneven padding. #​9821 (h/t @​allison-strandberg)
• Fix HTTP support when running GL JS against Mapbox Atlas. #​10090
• Fix a bug where the within expression didn't work in querySourceFeatures. #​9933
• Fix a bug where Popup content HTML element was removed on setDOMContent. #​10036
• Fix a compatibility bug when icon-image is used as a legacy categorical function. #​10060
• Reduce rapid memory growth in Safari by ensuring Image dataURI's are released. #​10118

⚠️ Note on IE11

We intend to remove support for Internet Explorer 11 in a future release of GL JS later this year.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
frontend-pwa	❌ Failed (Inspect)			Nov 21, 2023 1:59am

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @urbica/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"17.0.1" from the root project
npm ERR!   peer react@"*" from @testing-library/[email protected]
npm ERR!   node_modules/@testing-library/react
npm ERR!     dev @testing-library/react@"11.1.1" from the root project
npm ERR!   5 more (react-dom, react-map-gl, react-router, react-router-dom, react-transition-group)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.x" from @urbica/[email protected]
npm ERR! node_modules/@urbica/react-map-gl
npm ERR!   @urbica/react-map-gl@"1.14.2" from the root project
npm ERR!   peer @urbica/react-map-gl@"^1.0.0-alpha" from @urbica/[email protected]
npm ERR!   node_modules/@urbica/react-map-gl-cluster
npm ERR!     @urbica/react-map-gl-cluster@"0.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.x" from @urbica/[email protected]
npm ERR!   node_modules/@urbica/react-map-gl
npm ERR!     @urbica/react-map-gl@"1.14.2" from the root project
npm ERR!     peer @urbica/react-map-gl@"^1.0.0-alpha" from @urbica/[email protected]
npm ERR!     node_modules/@urbica/react-map-gl-cluster
npm ERR!       @urbica/react-map-gl-cluster@"0.2.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/c21adc/a28310/cache/others/npm/_logs/2023-11-21T01_54_32_701Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/c21adc/a28310/cache/others/npm/_logs/2023-11-21T01_54_32_701Z-debug-0.log