This is an automated email from the ASF dual-hosted git repository.

dashorst pushed a commit to branch wicket-11.x
in repository https://gitbox.apache.org/repos/asf/wicket.git


The following commit(s) were added to refs/heads/wicket-11.x by this push:
     new 2ab5f408aa Point AGENTS.md at the migration guides in the repository 
(#1906)
2ab5f408aa is described below

commit 2ab5f408aa527e00a34bd964ea2c584c476c87b5
Author: Martijn Dashorst <[email protected]>
AuthorDate: Sat Nov 14 20:21:50 2026 +0100

    Point AGENTS.md at the migration guides in the repository (#1906)
    
    AGENTS.md said the migration guide lives on the wiki, where only a human
    can put it, and asked for the wording in the commit message or the pull
    request description instead. The guides have since moved into the
    repository as migration-to-<major>.md in the root (#1815, #1816), and
    changes add their section there, as the PageParameters hash change did
    on master and on wicket-11.x. An agent following the old text left the
    guide alone and pointed at a wiki page that no longer exists.
    
    AGENTS.md now says that a change that breaks code or changes what a
    running application does adds its section to the branch's migration
    guide in the same change, and that on a maintenance branch the section
    goes under the releases after the .0.0.
    
    Generated-by: Claude Code (Claude Opus 5.5)
---
 AGENTS.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/AGENTS.md b/AGENTS.md
index 3c91a94d95..3f78b66adf 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -104,8 +104,9 @@ header — copy it when you add one.
   the new one, deprecate it rather than remove it.
 - An API change owes users a migration path. Add an OpenRewrite recipe to
   `wicket-migration/src/main/resources/META-INF/rewrite/wicket.yml` where the 
change is
-  mechanical, and draft the migration-guide wording in the commit message or 
the pull request
-  description — the guide itself lives on the wiki, where only a human can put 
it.
+  mechanical. A change that breaks code or changes what a running application 
does also gets a
+  section in the migration guide, `migration-to-<major>.md` in the root, in 
the same change. On a
+  maintenance branch it goes in the section for the releases after 
`<major>.0.0`.
 
 ## Javadoc
 

Reply via email to