search

vinayakkulkarni / v-mapbox

Vue-ish way for interacting with map(box|libre)-gl-js šŸ§­
https://v-mapbox.netlify.app/
MIT License
187 stars 45 forks source link

chore(deps): update dependency @deck.gl/core to v8.9.34 - autoclosed #1861

Closed renovate[bot] closed 9 months ago

renovate[bot] commented 10 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@deck.gl/core 8.9.23 -> 8.9.34 age adoption passing confidence

Release Notes

visgl/deck.gl (@​deck.gl/core) ### [`v8.9.34`](https://togithub.com/visgl/deck.gl/releases/tag/v8.9.34) [Compare Source](https://togithub.com/visgl/deck.gl/compare/v8.9.33...v8.9.34) - CARTO: fetchLayerData to support columns prop for query sources ([#​8412](https://togithub.com/visgl/deck.gl/issues/8412)) - v8 audit Layer#isLoaded implementations ([#​8290](https://togithub.com/visgl/deck.gl/issues/8290)) - CARTO: fix support for quantile color scale in numeric columns for static quadbin/h3 tilesets ([#​8347](https://togithub.com/visgl/deck.gl/issues/8347)) ### [`v8.9.33`](https://togithub.com/visgl/deck.gl/releases/tag/v8.9.33) [Compare Source](https://togithub.com/visgl/deck.gl/compare/v8.9.32...v8.9.33) - CARTO: added filter parameter to fetchLayerData ([#​8328](https://togithub.com/visgl/deck.gl/issues/8328)) - Improve Tile3DLayer.isLoaded ([#​8279](https://togithub.com/visgl/deck.gl/issues/8279)) - Fix pickObjects when using binary data ([#​8253](https://togithub.com/visgl/deck.gl/issues/8253)) - Use getCanvas() in GoogleMapsOverlay ([#​8272](https://togithub.com/visgl/deck.gl/issues/8272)) - Fix scripting interface error when canvas is invisible ([#​8254](https://togithub.com/visgl/deck.gl/issues/8254)) ### [`v8.9.32`](https://togithub.com/visgl/deck.gl/releases/tag/v8.9.32) [Compare Source](https://togithub.com/visgl/deck.gl/compare/v8.9.31...v8.9.32) - CARTO: Support styling layer by color column ([#​8177](https://togithub.com/visgl/deck.gl/issues/8177)) ### [`v8.9.31`](https://togithub.com/visgl/deck.gl/releases/tag/v8.9.31) [Compare Source](https://togithub.com/visgl/deck.gl/compare/v8.9.30...v8.9.31) - Draw mask layers when rendering to picking buffer ([#​8176](https://togithub.com/visgl/deck.gl/issues/8176)) - Export TripsLayerProps through geo-layer ([#​8175](https://togithub.com/visgl/deck.gl/issues/8175)) - Added a getCanvas helper function on deck ([#​7919](https://togithub.com/visgl/deck.gl/issues/7919)) - Fix issue where deck.gl blocks wheel scroll over non-interactive area ([#​8161](https://togithub.com/visgl/deck.gl/issues/8161)) - CARTO: Add carto module to `version` build script ([#​8123](https://togithub.com/visgl/deck.gl/issues/8123)) ### [`v8.9.30`](https://togithub.com/visgl/deck.gl/releases/tag/v8.9.30) [Compare Source](https://togithub.com/visgl/deck.gl/compare/v8.9.29...v8.9.30) - \[mapbox] fix drawing TerrainExtension in interleaved mode ([#​8115](https://togithub.com/visgl/deck.gl/issues/8115)) ### [`v8.9.29`](https://togithub.com/visgl/deck.gl/releases/tag/v8.9.29) [Compare Source](https://togithub.com/visgl/deck.gl/compare/v8.9.28...v8.9.29) - CARTO: Use null as default value for KeyValueObject ([#​8119](https://togithub.com/visgl/deck.gl/issues/8119)) ### [`v8.9.28`](https://togithub.com/visgl/deck.gl/releases/tag/v8.9.28) [Compare Source](https://togithub.com/visgl/deck.gl/compare/v8.9.27...v8.9.28) - \[mapbox] Fix interleaving when base map has terrain ([#​8111](https://togithub.com/visgl/deck.gl/issues/8111)) - Add typings for React render callback children ([#​8109](https://togithub.com/visgl/deck.gl/issues/8109)) - Upgrade luma.gl ([#​8112](https://togithub.com/visgl/deck.gl/issues/8112)) ### [`v8.9.27`](https://togithub.com/visgl/deck.gl/releases/tag/v8.9.27) [Compare Source](https://togithub.com/visgl/deck.gl/compare/v8.9.26...v8.9.27) - Added new numSegments prop in ArcLayer ([#​8055](https://togithub.com/visgl/deck.gl/issues/8055)) - Bump loaders.gl ([#​8087](https://togithub.com/visgl/deck.gl/issues/8087)) - Fix TileLayer isLoaded crash ([#​8074](https://togithub.com/visgl/deck.gl/issues/8074)) ### [`v8.9.26`](https://togithub.com/visgl/deck.gl/releases/tag/v8.9.26) [Compare Source](https://togithub.com/visgl/deck.gl/compare/v8.9.25...v8.9.26) - CARTO: Don't hardcode mime-types ([#​8076](https://togithub.com/visgl/deck.gl/issues/8076)) - CARTO: Polygon triangulation in CartoVectorTileLoader ([#​8064](https://togithub.com/visgl/deck.gl/issues/8064)) - DeckRenderer abort rendering when no views ([#​8065](https://togithub.com/visgl/deck.gl/issues/8065)) ### [`v8.9.25`](https://togithub.com/visgl/deck.gl/releases/tag/v8.9.25) [Compare Source](https://togithub.com/visgl/deck.gl/compare/v8.9.24...v8.9.25) - CARTO worker loaders ([#​8056](https://togithub.com/visgl/deck.gl/issues/8056)) ### [`v8.9.24`](https://togithub.com/visgl/deck.gl/releases/tag/v8.9.24) [Compare Source](https://togithub.com/visgl/deck.gl/compare/v8.9.23...v8.9.24) - Fix Scatterplot layer rendering on Xclipse 920 graphics ([#​8053](https://togithub.com/visgl/deck.gl/issues/8053))

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.

This PR has been generated by Mend Renovate. View repository job log here.

github-actions[bot] commented 10 months ago

āŒ @renovate[bot] the signed-off-by was not found in the following 1 commits:

šŸ“ What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

ā” Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'
github-actions[bot] commented 9 months ago

āŒ @renovate[bot] the signed-off-by was not found in the following 1 commits:

šŸ“ What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

ā” Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'
github-actions[bot] commented 9 months ago

āŒ @renovate[bot] the signed-off-by was not found in the following 1 commits:

šŸ“ What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

ā” Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'
github-actions[bot] commented 9 months ago

āŒ @renovate[bot] the signed-off-by was not found in the following 1 commits:

šŸ“ What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

ā” Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'
github-actions[bot] commented 9 months ago

āŒ @renovate[bot] the signed-off-by was not found in the following 1 commits:

šŸ“ What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

ā” Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'
github-actions[bot] commented 9 months ago

āŒ @renovate[bot] the signed-off-by was not found in the following 1 commits:

šŸ“ What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

ā” Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'