This is an automated email from the ASF dual-hosted git repository.
francischuang pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/calcite-avatica-go.git.
discard 36150dc [CALCITE-5059] Update Github Actions to latest versions
discard 9861e36 [CALCITE-5058] Upgrade dependencies and tidy go.mod
discard 8492d56 [CALCITE-5056] Test against avatica 1.18 - 1.20
new 1332e32 [CALCITE-5056] Test against avatica 1.18 - 1.20
new 3720c8c [CALCITE-5058] Upgrade dependencies and tidy go.mod
new 3abfabf [CALCITE-5059] Update Github Actions to latest versions
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 (36150dc)
\
N -- N -- N refs/heads/master (3abfabf)
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.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docker-compose.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
