This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 229341ef07 Minor: Regenerated BOMs for
fc211398e0ebcb75ea801d2a8050a982a13b311c
add 758d6cdc8e update SECURITY.md with feedback from ASF Security team
add e0bc3e603b Minor: Regenerated BOMs for
758d6cdc8e0e6912033463cdfc5dc123fc6b1b13
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 (229341ef07)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(e0bc3e603b)
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:
SECURITY.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
