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 683bc66f9 Version bump
discard 38b903ee4 Delete me: test build; release on workflow
discard a0133ce73 Extend native build for more Rubies
discard 32598c0b0 Update links in README
discard 09270f83d Push all native gems
discard 469b0d020 Fix tests in CI
discard 38b8171d0 Move middlewares to OpenDal::Middlware
discard 72d118b4e Fix metadata's inspect
discard f99d9c0b5 Fix release workflows
add 21cae0f76 Fix release workflows
add c2ad8b5bf Fix metadata's inspect
add 453f370a9 Move middlewares to OpenDal::Middlware
add 89a40516b Fix tests in CI
add 330bc0090 Push all native gems
add b82165e84 Update links in README
add 30c0c442b Extend native build for more Rubies
add cbd53cd46 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 (683bc66f9)
\
N -- N -- N refs/heads/publish-ruby-binding (cbd53cd46)
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 | 20 ++++++++++++++++++--
bindings/ruby/Cargo.toml | 2 +-
2 files changed, 19 insertions(+), 3 deletions(-)
