Skip to content

chore(deps): bump opendal to 0.58.1 #23601

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
benjyw merged 3 commits into from
Aug 25, 2026
+101 −56
Merged

chore(deps): bump opendal to 0.58.1 #23601

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
782f003
chore(deps): bump opendal to 0.58.1
Xuanwo Aug 4, 2026
7b6946a
docs: note OpenDAL 0.58.1 upgrade in 2.34.x release notes
Xuanwo Aug 4, 2026
1fc83ab
chore: drop user-facing notes and migration comment
Xuanwo Aug 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/notes/2.34.x.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,8 @@ Thank you to [Klaviyo](https://www.klaviyo.com/) for their Platinum tier support

### 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.

@benjyw benjyw Aug 15, 2026

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?

@Xuanwo Xuanwo Aug 25, 2026

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?


Fixed a bug where `SingleSourceField` could not be hydrated for generated targets because files were validated before code generation ran.

Fixed an issue where `pants --changed-since` would unnecessarily invalidate all targets in a `BUILD` file when only whitespace or comment lines were modified.
Expand Down
Loading
Loading