This is an automated email from the ASF dual-hosted git repository.
erickguan pushed a change to branch publish-ruby-binding
in repository https://gitbox.apache.org/repos/asf/opendal.git
discard cbd53cd46 Version bump
discard 30c0c442b Extend native build for more Rubies
discard b82165e84 Update links in README
discard 330bc0090 Push all native gems
discard 89a40516b Fix tests in CI
discard 453f370a9 Move middlewares to OpenDal::Middlware
discard c2ad8b5bf Fix metadata's inspect
discard 21cae0f76 Fix release workflows
add 80a1a1906 Fix release workflows
add 82ffdf408 Fix metadata's inspect
add b783e1bc7 Move middlewares to OpenDal::Middlware
add ca1ffd7dc Fix tests in CI
add 3ab072bf6 Push all native gems
add c76c74753 Update links in README
add c13bd1c39 Extend native build for more Rubies
add 7b5eff764 Version bump
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 (cbd53cd46)
\
N -- N -- N refs/heads/publish-ruby-binding (7b5eff764)
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:
.github/workflows/release_ruby.yml | 2 +-
bindings/ruby/Cargo.toml | 2 +-
bindings/ruby/opendal.gemspec | 12 ++++++++----
3 files changed, 10 insertions(+), 6 deletions(-)
