You are viewing a plain text version of this content. The canonical link for it is here.

Posted to cvs@httpd.apache.org by co...@apache.org on 2023/01/17 18:19:56 UTC

svn commit: r1906743 - /httpd/dev-tools/release/r4-stage-release.sh

Author: covener
Date: Tue Jan 17 18:19:56 2023
New Revision: 1906743

URL: http://svn.apache.org/viewvc?rev=1906743&view=rev
Log:
use v5 schema for timeline entry flagging the release


Modified:
    httpd/dev-tools/release/r4-stage-release.sh

Modified: httpd/dev-tools/release/r4-stage-release.sh
URL: http://svn.apache.org/viewvc/httpd/dev-tools/release/r4-stage-release.sh?rev=1906743&r1=1906742&r2=1906743&view=diff
==============================================================================
--- httpd/dev-tools/release/r4-stage-release.sh (original)
+++ httpd/dev-tools/release/r4-stage-release.sh Tue Jan 17 18:19:56 2023
@@ -162,7 +162,8 @@ if test -n "${CVE_DIRS}"; then
       echo "adding ${CVE_ID}"
       # add a timeline entry for the release and copy to website
       rm -f "${CVE_JSON}".tmp
-      jq --indent 2 '.timeline[.timeline|length] |= . + '"${TIMELINE_ENTRY}" "${CVE_JSON}" > "${CVE_JSON}".tmp
+      # XXX: Untested, during 2.4.55 we noticed .timeline was used which is not in the schema.
+      jq --indent 2 '.containers.cna.timeline[.containers.cna.timeline|length] |= . + '"${TIMELINE_ENTRY}" "${CVE_JSON}" > "${CVE_JSON}".tmp
       mv "${CVE_JSON}".tmp "${CVE_JSON}"
       cp "${CVE_JSON}" "${DIST_SITEPATH}"/content/security/json/${CVE_ID}.json
     done