This is an automated email from the ASF dual-hosted git repository. dashorst pushed a commit to branch wicket-11.x-setup in repository https://gitbox.apache.org/repos/asf/wicket.git
commit c60f7c375f5a52177345a227f806b58270c0da60 Author: Martijn Dashorst <[email protected]> AuthorDate: Tue Nov 3 22:41:13 2026 +0100 Name the release branch, not master, as home of the current line SECURITY.md said the current line is developed on master and asked reporters to verify a finding against master. With the 11.x line now on its own wicket-11.x branch, master carries the next major release, which is unreleased and not a supported line. A finding verified only against master would be verified against code no release line contains. The current line is now described like the LTS line, as maintained on its wicket-<major>.x branch, and reporters verify against that branch. Generated-by: Claude Code (Claude Opus 5.5) --- SECURITY.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index 8f5bc92590..d2780db8d3 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -65,8 +65,8 @@ needs fixing. Security fixes are applied to two release lines: -- the **current** line, the most recent major release, developed on `master`. - It is supported until the next major release. +- the **current** line, the most recent major release, maintained on its + `wicket-<major>.x` branch. It is supported until the next major release. - the **long-term support (LTS)** line, maintained on its `wicket-<major>.x` branch. It is supported until the next LTS release. @@ -219,7 +219,7 @@ that can, and neither is a judgement on whether the concern behind it is real. ### A finding must be verified against a supported branch tip Verify the issue against the current tip of the line you are reporting against: -`master` for the current line, or the `wicket-<major>.x` branch of the LTS line. +the `wicket-<major>.x` branch of the current line or of the LTS line. One of them is enough — say which, and name the commit you tested. A failing test against that commit is ideal. Reporting only the release you happen to be running is not sufficient: a released artifact is always behind its branch, and
