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

rombert pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git


The following commit(s) were added to refs/heads/master by this push:
     new 71cee000 fix(skills): there is only update wiki page for parent pom 
updates
71cee000 is described below

commit 71cee0004d2f4d8ba03b5f828802f728462d410c
Author: Robert Munteanu <[email protected]>
AuthorDate: Mon Oct 12 21:00:30 2026 +0100

    fix(skills): there is only update wiki page for parent pom updates
    
    Use a direct reference, don't let the agents hunt aroud needlessly.
---
 skills/update-sling-parent-pom/SKILL.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/skills/update-sling-parent-pom/SKILL.md 
b/skills/update-sling-parent-pom/SKILL.md
index 03ba3e3a..2df3f9bc 100644
--- a/skills/update-sling-parent-pom/SKILL.md
+++ b/skills/update-sling-parent-pom/SKILL.md
@@ -21,7 +21,7 @@ Use when the user asks to upgrade the Sling parent POM 
version in their project.
 - identify the current version of the Sling parent POM in the user's project
 - determine the latest available Sling parent POM version for the applicable 
parent artifact
     - target the latest available version, not merely the next increment
-- check `https://cwiki.apache.org/confluence/spaces/SLING/pages/` for an 
official "Update to Parent NN" migration page covering a version between the 
current and target (search or ask the user; these pages are not sequentially 
numbered). Follow any steps it documents that are not already covered by this 
skill's reference files
+- check 
`https://cwiki.apache.org/confluence/spaces/SLING/pages/284790344/Update+to+Parent+60`for
 additional instructions. Follow any steps it documents that are not already 
covered by this skill's reference files
 - update the parent POM version
 - run `mvn validate` with the current Java version before running a full build
     - if `mvn validate` fails, fix any POM syntax issues first

Reply via email to