This is an automated email from the ASF dual-hosted git repository.
nicholasjiang pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/paimon-webui.git
discard e5e0f984 [Improvement] Remove project.version property (#535)
discard 24febe48 [Improvement] Introduce apache-release and docs-and-source
profile (#534)
omit 75e6a3c3 [improvement] Introduce explanation of additional
dependencies in Quick Start (#533)
omit d7a38131 [Bugfix] Fix playground NullPointerException (#530)
omit 06d18a8c [Release] Support binary releasing of Paimon WebUI (#529)
new 5d1fea3d [Bugfix] Fix playground NullPointerException (#530)
new 72159c2f [improvement] Introduce explanation of additional
dependencies in Quick Start (#533)
new fd3611e4 [Improvement] Introduce apache-release and docs-and-source
profile (#534)
new 4f3c4a34 [Improvement] Remove project.version property (#535)
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 (e5e0f984)
\
N -- N -- N refs/heads/main (4f3c4a34)
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 4 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:
pom.xml | 2 +-
.../{create_release_package.sh => create_source_release.sh} | 7 ++-----
2 files changed, 3 insertions(+), 6 deletions(-)
rename tools/releasing/{create_release_package.sh => create_source_release.sh}
(86%)
