You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sedona.apache.org by "dependabot[bot] (via GitHub)" <gi...@apache.org> on 2025/11/30 20:10:04 UTC
[PR] chore(deps): bump criterion from 0.5.1 to 0.8.0 [sedona-db]
dependabot[bot] opened a new pull request, #397:
URL: https://github.com/apache/sedona-db/pull/397
Bumps [criterion](https://github.com/criterion-rs/criterion.rs) from 0.5.1 to 0.8.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/criterion-rs/criterion.rs/releases">criterion's releases</a>.</em></p>
<blockquote>
<h2>criterion-plot-v0.8.0</h2>
<p>No release notes provided.</p>
<h2>criterion-v0.8.0</h2>
<h3>BREAKING</h3>
<ul>
<li>Drop async-std support</li>
</ul>
<h3>Changed</h3>
<ul>
<li>Bump MSRV to 1.86, stable to 1.91.1</li>
</ul>
<h3>Added</h3>
<ul>
<li>Add ability to plot throughput on summary page.</li>
<li>Add support for reporting throughput in elements and bytes - <code>Throughput::ElementsAndBytes</code> allows the text summary to report throughput in both units simultaneously.</li>
<li>Add alloca-based memory layout randomisation to mitigate memory effects on measurements.</li>
<li>Add doc comment to benchmark runner in criterion_group macro (removes linter warnings)</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Fix plotting NaN bug</li>
</ul>
<h3>Other</h3>
<ul>
<li>Remove Master API Docs links temporarily while we restore the docs publishing.</li>
</ul>
<h2>criterion-plot-v0.7.0</h2>
<p>No release notes provided.</p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/criterion-rs/criterion.rs/blob/master/CHANGELOG.md">criterion's changelog</a>.</em></p>
<blockquote>
<h2><a href="https://github.com/criterion-rs/criterion.rs/compare/criterion-v0.7.0...criterion-v0.8.0">0.8.0</a> - 2025-11-29</h2>
<h3>BREAKING</h3>
<ul>
<li>Drop async-std support</li>
</ul>
<h3>Changed</h3>
<ul>
<li>Bump MSRV to 1.86, stable to 1.91.1</li>
</ul>
<h3>Added</h3>
<ul>
<li>Add ability to plot throughput on summary page.</li>
<li>Add support for reporting throughput in elements and bytes - <code>Throughput::ElementsAndBytes</code> allows the text summary to report throughput in both units simultaneously.</li>
<li>Add alloca-based memory layout randomisation to mitigate memory effects on measurements.</li>
<li>Add doc comment to benchmark runner in criterion_group macro (removes linter warnings)</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Fix plotting NaN bug</li>
</ul>
<h3>Other</h3>
<ul>
<li>Remove Master API Docs links temporarily while we restore the docs publishing.</li>
</ul>
<h2>[0.7.0] - 2025-07-25</h2>
<ul>
<li>Bump version of criterion-plot to align dependencies.</li>
</ul>
<h2>[0.6.0] - 2025-05-17</h2>
<h3>Changed</h3>
<ul>
<li>MSRV bumped to 1.80</li>
<li>The <code>real_blackbox</code> feature no longer has any impact. Criterion always uses <code>std::hint::black_box()</code> now.
Users of <code>criterion::black_box()</code> should switch to <code>std::hint::black_box()</code>.</li>
<li><code>clap</code> dependency unpinned.</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>gnuplot version is now correctly detected when using certain Windows binaries/configurations that used to fail</li>
</ul>
<h3>Added</h3>
<ul>
<li>Async benchmarking with Tokio may be done via a <code>tokio::runtime::Handle</code>, not only a <code>tokio::runtime::Runtime</code></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/criterion-rs/criterion.rs/commit/b49ade728c064f49cb2a70b0368658a15cf21833"><code>b49ade7</code></a> chore: release v0.8.0</li>
<li><a href="https://github.com/criterion-rs/criterion.rs/commit/c56485f567ebda16f1ae16ec0b9d80c9465f0f87"><code>c56485f</code></a> docs: Mark Master API Docs links that need to be updated</li>
<li><a href="https://github.com/criterion-rs/criterion.rs/commit/86526a42d8270c41682e44b2a31d39a3f94a0829"><code>86526a4</code></a> docs: Remove Master API Docs link temporarily</li>
<li><a href="https://github.com/criterion-rs/criterion.rs/commit/00a443f8bc172fdf5803926ce2ac244b95cbad49"><code>00a443f</code></a> docs: Update README links</li>
<li><a href="https://github.com/criterion-rs/criterion.rs/commit/21ca33120871e02936ad68fd4d3c7513fdb9d69c"><code>21ca331</code></a> feat: Add release-plz publish action</li>
<li><a href="https://github.com/criterion-rs/criterion.rs/commit/6c2bc97d841097a32c86c66b45cf46d2904111eb"><code>6c2bc97</code></a> docs: Add alloca explanation</li>
<li><a href="https://github.com/criterion-rs/criterion.rs/commit/61804497c9117bf572079c36ef9ab0436a2a5383"><code>6180449</code></a> fix: Remove dubious loop limitation</li>
<li><a href="https://github.com/criterion-rs/criterion.rs/commit/bcefede1648b6b59f405db77c019c7c52613bf6f"><code>bcefede</code></a> limit stackalloc to page size</li>
<li><a href="https://github.com/criterion-rs/criterion.rs/commit/46d3ff07447bb784da984742d63997750c17e801"><code>46d3ff0</code></a> use alloca only in windows and unix</li>
<li><a href="https://github.com/criterion-rs/criterion.rs/commit/7d39b2a98359c518738b3ee7a83c1794ae72ffe8"><code>7d39b2a</code></a> offset tests with alloca</li>
<li>Additional commits viewable in <a href="https://github.com/criterion-rs/criterion.rs/compare/0.5.1...criterion-v0.8.0">compare view</a></li>
</ul>
</details>
<br />
[](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: issues-unsubscribe@sedona.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] chore(deps): bump criterion from 0.5.1 to 0.8.0 [sedona-db]
Posted by "paleolimbot (via GitHub)" <gi...@apache.org>.
paleolimbot closed pull request #397: chore(deps): bump criterion from 0.5.1 to 0.8.0
URL: https://github.com/apache/sedona-db/pull/397
--
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: issues-unsubscribe@sedona.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] chore(deps): bump criterion from 0.5.1 to 0.8.0 [sedona-db]
Posted by "paleolimbot (via GitHub)" <gi...@apache.org>.
paleolimbot commented on PR #397:
URL: https://github.com/apache/sedona-db/pull/397#issuecomment-3602820007
I just closed them all until I can update the DataFusion version. Mostly we just align our dependencies to DataFusion (because if we specify a different version sometimes things don't work or we end up compiling two versions of the same crate).
--
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: issues-unsubscribe@sedona.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] chore(deps): bump criterion from 0.5.1 to 0.8.0 [sedona-db]
Posted by "dependabot[bot] (via GitHub)" <gi...@apache.org>.
dependabot[bot] commented on PR #397:
URL: https://github.com/apache/sedona-db/pull/397#issuecomment-3602667509
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
--
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: issues-unsubscribe@sedona.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] chore(deps): bump criterion from 0.5.1 to 0.8.0 [sedona-db]
Posted by "petern48 (via GitHub)" <gi...@apache.org>.
petern48 commented on PR #397:
URL: https://github.com/apache/sedona-db/pull/397#issuecomment-3602799422
@paleolimbot I'm curious. What thought process do you go through to decide whether to merge these dependency updates or not? Assuming CI passes cleanly. Some factors that may come to mind:
- How large of a version bump it is
- What the package is
--
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: issues-unsubscribe@sedona.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org