This is an automated email from the ASF dual-hosted git repository.
lidavidm pushed a change to branch maint-23
in repository https://gitbox.apache.org/repos/asf/arrow-adbc.git
omit 318f455ad chore: update versions for 23
omit 04b10ef17 chore: update CHANGELOG.md for 23
add 8b056e1b5 chore(go/adbc): bump github.com/go-jose/go-jose/v3 from
3.0.4 to 3.0.5 in /go/adbc (#4177)
add 725836233 chore: update CHANGELOG.md for 23
add efdc10ba9 chore: update versions for 23
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 (318f455ad)
\
N -- N -- N refs/heads/maint-23 (efdc10ba9)
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:
ci/linux-packages/debian/changelog | 2 +-
go/adbc/go.mod | 2 +-
go/adbc/go.sum | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
