This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/cargo/criterion-0.8.1
in repository https://gitbox.apache.org/repos/asf/sedona-db.git
discard 00fe0589 chore(deps): bump criterion from 0.5.1 to 0.8.1
add fd0ea070 docs(r): update installation command (#421)
add c68fbfc0 chore(deps): bump savvy-* to v0.9 (#426)
add 80db6884 chore: Update versions on main for 0.3.0 (#411)
add 06c70408 chore(deps): bump criterion from 0.5.1 to 0.8.1
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (00fe0589)
\
N -- N -- N refs/heads/dependabot/cargo/criterion-0.8.1
(06c70408)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
Cargo.lock | 1033 +++++++++++++++++++++---------------------------
Cargo.toml | 42 +-
docs/index.md | 2 +-
r/sedonadb/DESCRIPTION | 2 +-
r/sedonadb/README.Rmd | 7 +
r/sedonadb/README.md | 44 ++-
6 files changed, 506 insertions(+), 624 deletions(-)
