This is an automated email from the ASF dual-hosted git repository.
arm pushed a change to branch previous_sbom_results
in repository https://gitbox.apache.org/repos/asf/tooling-trusted-releases.git
discard 6d267b9 Show previous/changed licenses
discard b9e4de2 Add some colour to the report and add icon helper to htm
discard c552114 Abstract task fetches
discard 0218edb Show change from previous severity and change defaults for
previous license info
discard 129c2da Don't need keys()
discard b508730 Fix non-digit character handling in version_sort_key
discard 837d129 Highlight new/updated vulnerabilities and colour code
severities
discard 1ce2be5 Find previous results and include in score result for report.
new 3f2a259 Pull previous SBOM results into the report and highlight
new/changed vulnerabilities and licenses.
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 (6d267b9)
\
N -- N -- N refs/heads/previous_sbom_results (3f2a259)
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 1 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:
atr/get/sbom.py | 1 +
1 file changed, 1 insertion(+)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
