Skip to content

chore(deps): bump opendal to 0.58.1 - #23601

Merged
benjyw merged 3 commits into
pantsbuild:mainfrom
Xuanwo:xuanwo/chore-bump-opendal-0.58.1
Aug 25, 2026
Merged

chore(deps): bump opendal to 0.58.1#23601
benjyw merged 3 commits into
pantsbuild:mainfrom
Xuanwo:xuanwo/chore-bump-opendal-0.58.1

Conversation

@Xuanwo

@Xuanwo Xuanwo commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Bump the workspace OpenDAL dependency from 0.57.0 to 0.58.1 so Pants tracks the current stable release for the experimental file and GitHub Actions Cache remote providers.

OpenDAL 0.58 returns a finished Operator from Operator::new, so construction no longer calls finish() after layering. Feature pins are unchanged (layers-*, services-memory/fs/ghac, default-features = false).

This keeps the remote store path on a maintained OpenDAL line and picks up the 0.58.1 crate-split / layer packaging fixes without changing provider behavior beyond the constructor API adaptation.

Update the workspace OpenDAL pin and adapt Operator construction to the
0.58 API where Operator::new returns a finished operator (no finish()).
@Xuanwo
Xuanwo marked this pull request as ready for review August 4, 2026 09:43
@Xuanwo

Xuanwo commented Aug 8, 2026

Copy link
Copy Markdown
Contributor Author

Hello @benjyw, I’m the OpenDAL maintainer, and I hope you’re happy with OpenDAL. We’ve recently made some good improvements, and I hope Pandas can benefit from them. Thank you in advance for the review.

@benjyw benjyw left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for this - I think we can get rid of some of the verbiage and keep it simple.

Comment thread docs/notes/2.34.x.md Outdated

### General

The [OpenDAL](https://opendal.apache.org/) library powering the experimental file and GitHub Actions Cache remote store providers has been upgraded from 0.57.0 to 0.58.1.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We can delete this release notes update - this change will be invisible to end users and plugin developers I think?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Dropped. This is an internal crate bump, so I agree it does not belong in user-facing notes.

I don't have permission to add labels here. Could you add release-notes:not-required so CI stays green without the notes file change?

scope: String,
options: RemoteStoreOptions,
) -> Result<Provider, String> {
// Operator::new returns a finished operator in OpenDAL 0.58+; layers are

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This comment might be more confusing than illuminating. It makes sense in the context of this PR, but a future reader won't have the pre-0.58 context, so they will not know what this information is for. I think it's fine to delete.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Agreed, removed.

@benjyw benjyw added the release-notes:not-required [CI] PR doesn't require mention in release notes label Aug 15, 2026
Address review: this OpenDAL bump is internal, and the Operator::new
comment is only useful in the context of the 0.58 migration.
@benjyw
benjyw merged commit 49181d1 into pantsbuild:main Aug 25, 2026
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-notes:not-required [CI] PR doesn't require mention in release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants