Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 7, 2024

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

Compare Source

  • CARTO: fetchLayerData to support columns prop for query sources (#​8412)
  • v8 audit Layer#isLoaded implementations (#​8290)
  • CARTO: fix support for quantile color scale in numeric columns for static quadbin/h3 tilesets (#​8347)

v8.9.33

Compare Source

  • CARTO: added filter parameter to fetchLayerData (#​8328)
  • Improve Tile3DLayer.isLoaded (#​8279)
  • Fix pickObjects when using binary data (#​8253)
  • Use getCanvas() in GoogleMapsOverlay (#​8272)
  • Fix scripting interface error when canvas is invisible (#​8254)

v8.9.32

Compare Source

  • CARTO: Support styling layer by color column (#​8177)

v8.9.31

Compare Source

  • Draw mask layers when rendering to picking buffer (#​8176)
  • Export TripsLayerProps through geo-layer (#​8175)
  • Added a getCanvas helper function on deck (#​7919)
  • Fix issue where deck.gl blocks wheel scroll over non-interactive area (#​8161)
  • CARTO: Add carto module to version build script (#​8123)

v8.9.30

Compare Source

  • [mapbox] fix drawing TerrainExtension in interleaved mode (#​8115)

v8.9.29

Compare Source

  • CARTO: Use null as default value for KeyValueObject (#​8119)

v8.9.28

Compare Source

  • [mapbox] Fix interleaving when base map has terrain (#​8111)
  • Add typings for React render callback children (#​8109)
  • Upgrade luma.gl (#​8112)

v8.9.27

Compare Source

v8.9.26

Compare Source

  • CARTO: Don't hardcode mime-types (#​8076)
  • CARTO: Polygon triangulation in CartoVectorTileLoader (#​8064)
  • DeckRenderer abort rendering when no views (#​8065)

v8.9.25

Compare Source

v8.9.24

Compare Source

  • Fix Scatterplot layer rendering on Xclipse 920 graphics (#​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.


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

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

Copy link

github-actions bot commented Jan 7, 2024

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

  • aee18f2: chore(deps): update dependency @deck.gl/core to v8.9.33

📝 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 <[email protected]>

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'

@renovate renovate bot force-pushed the renovate/deck.gl-core-8.x-lockfile branch from aee18f2 to a40fe65 Compare January 19, 2024 20:54
@renovate renovate bot changed the title chore(deps): update dependency @deck.gl/core to v8.9.33 chore(deps): update dependency @deck.gl/core to v8.9.34 Jan 19, 2024
Copy link

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

  • a40fe65: chore(deps): update dependency @deck.gl/core to v8.9.34

📝 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 <[email protected]>

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'

2 similar comments
Copy link

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

  • a40fe65: chore(deps): update dependency @deck.gl/core to v8.9.34

📝 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 <[email protected]>

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'

Copy link

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

  • a40fe65: chore(deps): update dependency @deck.gl/core to v8.9.34

📝 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 <[email protected]>

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'

@renovate renovate bot force-pushed the renovate/deck.gl-core-8.x-lockfile branch from a40fe65 to 80f8490 Compare January 29, 2024 19:53
Copy link

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

  • 80f8490: chore(deps): update dependency @deck.gl/core to v8.9.34

📝 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 <[email protected]>

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'

@renovate renovate bot changed the title chore(deps): update dependency @deck.gl/core to v8.9.34 chore(deps): update dependency @deck.gl/core to v8.9.34 - autoclosed Feb 4, 2024
@renovate renovate bot closed this Feb 4, 2024
@renovate renovate bot deleted the renovate/deck.gl-core-8.x-lockfile branch February 4, 2024 13:20
Copy link

github-actions bot commented Feb 4, 2024

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

  • 80f8490: chore(deps): update dependency @deck.gl/core to v8.9.34

📝 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 <[email protected]>

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'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants