Skip to content

Conversation

@dentiny
Copy link
Contributor

@dentiny dentiny commented Aug 3, 2025

What changes are included in this PR?

This PR upgrades roaring dependency from 0.10 to 0.11.

Motivation:

  • Latest roaring v0.11 includes all features described in spec, including run container which is only supported in v0.11
  • I do notice iceberg-rust has configured dependabot and triggers on weekly basic, but doesn't seem to upgrade this particular crate for a while
    • The v0.11 was release 6 weeks ago, which I expect to upgrade with no human intervene

I checked there's one version for roaring.

Another change I made is to switch from <major>.<minor>.<patch> to <major>.<minor>;
I do notice cargo is very good at figuring out a crate version which works for all or most dependency requirements.
A precise version requirement is easy to lead to multiple versions for one single crate.

Are these changes tested?

No op change, CI should be enough.

Copy link
Contributor

@liurenjie1024 liurenjie1024 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dentiny for this pr!

@liurenjie1024 liurenjie1024 merged commit 492c1a3 into apache:main Aug 4, 2025
18 checks passed
Yiyang-C pushed a commit to Yiyang-C/iceberg-rust that referenced this pull request Aug 26, 2025
## What changes are included in this PR?

This PR upgrades `roaring` dependency from 0.10 to 0.11.

Motivation:
- Latest roaring v0.11 includes all features described in spec,
including `run container` which is only supported in v0.11
+ See v0.11 release notes:
https://github.com/RoaringBitmap/roaring-rs/releases
+ The missing feature blocks iceberg-rust to read deletion vector puffin
blob written by other engines
- I do notice iceberg-rust has configured dependabot and triggers on
weekly basic, but doesn't seem to upgrade this particular crate for a
while
+ The v0.11 was release 6 weeks ago, which I expect to upgrade with no
human intervene

I checked there's one version for `roaring`.

Another change I made is to switch from `<major>.<minor>.<patch>` to
`<major>.<minor>`;
I do notice `cargo` is very good at figuring out a crate version which
works for all or most dependency requirements.
A precise version requirement is easy to lead to multiple versions for
one single crate.

## Are these changes tested?

No op change, CI should be enough.
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.

2 participants