dependabot[bot] opened a new pull request, #393:
URL: https://github.com/apache/sedona-db/pull/393

   Bumps [savvy](https://github.com/yutannihilation/savvy) from 0.8.13 to 0.9.0.
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/yutannihilation/savvy/blob/main/CHANGELOG.md";>savvy's 
changelog</a>.</em></p>
   <blockquote>
   <h2>[v0.9.0] (2025-11-24)</h2>
   <h3>New features</h3>
   <ul>
   <li>The R object generated from a Rust struct now has one additional S3 
class <code>PKG_NAME::STRUCT_NAME</code> in addition to the bare struct name. 
This is useful if you want to avoid name collisions between packages. Thanks <a 
href="https://github.com/eitsupi";><code>@​eitsupi</code></a>! (<a 
href="https://redirect.github.com/yutannihilation/savvy/issues/404";>#404</a>)</li>
   </ul>
   <h3>Minor improvements</h3>
   <ul>
   <li>Bump MSRV to 1.81 and remove the dependency of rustversion crate (<a 
href="https://redirect.github.com/yutannihilation/savvy/issues/412";>#412</a>).</li>
   </ul>
   <h2>[v0.8.14] (2025-10-25)</h2>
   <h3>New features</h3>
   <ul>
   <li><code>savvy-cli</code> got a new optional argument to specify the path 
to the Rust code dir (<a 
href="https://redirect.github.com/yutannihilation/savvy/issues/402";>#402</a>).</li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/yutannihilation/savvy/commit/683e4488744f8b4ceb58b211e47ec4db7acc0291";><code>683e448</code></a>
 chore: Release</li>
   <li><a 
href="https://github.com/yutannihilation/savvy/commit/026cc6a8cffb9afa3767dd2bc243e27518b85793";><code>026cc6a</code></a>
 Bump MSRV to 1.81 and fix clippy warning (<a 
href="https://redirect.github.com/yutannihilation/savvy/issues/412";>#412</a>)</li>
   <li><a 
href="https://github.com/yutannihilation/savvy/commit/11ad4dfcb64a21bbdeb13ed0a414adfe3f33ddf8";><code>11ad4df</code></a>
 docs: Update documents (<a 
href="https://redirect.github.com/yutannihilation/savvy/issues/411";>#411</a>)</li>
   <li><a 
href="https://github.com/yutannihilation/savvy/commit/4bf17536215986d64b28009d93d5fdd451052a23";><code>4bf1753</code></a>
 Update cargo-dist to v0.30.2 (<a 
href="https://redirect.github.com/yutannihilation/savvy/issues/410";>#410</a>)</li>
   <li><a 
href="https://github.com/yutannihilation/savvy/commit/7195a0a46f595b15f81d277b21ef9642639c234c";><code>7195a0a</code></a>
 chore(cli): Remove <code>remove_old_wrapper_r()</code> (<a 
href="https://redirect.github.com/yutannihilation/savvy/issues/409";>#409</a>)</li>
   <li><a 
href="https://github.com/yutannihilation/savvy/commit/f3efbd45193544a3a6e24b195f0d16b3ebcadd56";><code>f3efbd4</code></a>
 feat(savvy-cli): add package name prefixed class names (<a 
href="https://redirect.github.com/yutannihilation/savvy/issues/404";>#404</a>)</li>
   <li><a 
href="https://github.com/yutannihilation/savvy/commit/712859d2bbddbf4afbf58cc6cc81eef524bd6e65";><code>712859d</code></a>
 init (<a 
href="https://redirect.github.com/yutannihilation/savvy/issues/405";>#405</a>)</li>
   <li><a 
href="https://github.com/yutannihilation/savvy/commit/8aa35b97144a007976149613abc87b2be3a98223";><code>8aa35b9</code></a>
 Kudos to extendr!</li>
   <li><a 
href="https://github.com/yutannihilation/savvy/commit/bde22c3bca2a6147e6a8f89fcc81dfdbbdd9e1b8";><code>bde22c3</code></a>
 chore: Release</li>
   <li><a 
href="https://github.com/yutannihilation/savvy/commit/c4c170d4b66404349a9ca5e6b275e44d9ceb0734";><code>c4c170d</code></a>
 Add <code>rust_dir</code> argument to <code>savvy-cli update</code> (<a 
href="https://redirect.github.com/yutannihilation/savvy/issues/402";>#402</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/yutannihilation/savvy/compare/v0.8.13...v0.9.0";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=savvy&package-manager=cargo&previous-version=0.8.13&new-version=0.9.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   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-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   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)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to