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 e18096623 Version bump
discard 043d3211d fix
discard 76cb4c794 build
discard 672f47c24 build
discard 069bba8f0 build
discard 7cec4d9e6 build
discard a9ee2e7ad Fix rb-sys
discard 1a5245a6a pre built task
discard 980a9f8ab debug
discard 36e88706f debug
discard f68f07e3a debug
discard 1b4995089 Fix workflow
discard b6215c6b5 debug
discard 6c47a0018 s: Explicit workflow updates
discard 72a853de0 Allow release workflow downloading artifacts
add ce8e4119e Fix release workflows
add 41fef41d6 Version bump
add 65068e185 Fix tests in CI
add 97b325dc4 Push all native gems
add d77f0dab7 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 (e18096623)
\
N -- N -- N refs/heads/publish-ruby-binding (d77f0dab7)
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:
bindings/ruby/Cargo.toml | 2 +-
bindings/ruby/Rakefile | 24 +++++++++++++++++++++++-
2 files changed, 24 insertions(+), 2 deletions(-)
