[ 
https://issues.apache.org/jira/browse/CAMEL-27347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18148829#comment-18148829
 ] 

Claus Ibsen commented on CAMEL-27347:
-------------------------------------

Merged to main in https://github.com/apache/camel/pull/30561 (commit 
097335aff4), for 4.24.0.

_Claude Code on behalf of davsclaus_

> camel-catalog - keep the security advisories and known releases in sync with 
> camel-website before each release
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-27347
>                 URL: https://issues.apache.org/jira/browse/CAMEL-27347
>             Project: Camel
>          Issue Type: Task
>          Components: camel-catalog
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 4.24.0
>
>
> The Apache Camel security advisories that ship with camel-catalog 
> ({{advisories/camel-security-advisories.json}}) are generated from the 
> advisories of the camel-website repository ({{content/security/*.md}}) by the 
> {{update-security-advisories}} goal, in the opt-in profile 
> {{-Pupdate-security-advisories}} of camel-catalog. Nothing runs it: on main 
> the JSON has 76 advisories, the newest of 2026-07-05, while camel-website has 
> 137 advisory files (newest CVE-2026-95664). The CVE audit of the CLI, the TUI 
> and the MCP server therefore misses the recent Camel CVEs and their upgrade 
> advice.
> The known releases ({{releases/camel-releases.json}}, 
> {{-Pupdate-camel-releases}}) are current today, but only because someone runs 
> the profile by hand.
> h4. Proposal
> * Regenerate both now.
> * A scheduled GitHub workflow (weekly, as the SBOM one) runs the sync goals 
> on main (advisories and releases) and on the LTS branches (releases; they 
> have no advisories), and opens a PR when something changed.
> * The release guide runs both profiles before {{release:prepare}}.
> * The sync goals use {{GITHUB_TOKEN}} when set, so a CI runner is not limited 
> by the anonymous GitHub API rate limit.
> Checking the advisories online at audit time, with the catalog as the 
> fallback, is a separate JIRA.
> _Claude Code on behalf of Claus Ibsen (davsclaus)_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to