[Misc] Record the dependency-upgrade commit prefix and issue description rules

A dependency bump was committed as [Misc] because the dependency was declared through a pnpm
catalog entry, which hides whether it is a runtime or a dev-only dependency; and the issue that
replaced it linked only the target release, losing the five intermediate releases the bump crosses.

* commit-messages: split dependency upgrades on the existing user-visible test — dev/peer/test-scoped
  is [Misc], anything in dependencies or a runtime Maven dependency needs an issue — and warn that a
  shared version catalog hides which one it is.
* jira: add the dependency-upgrade issue shape (summary, Dependency Upgrades component, description
  = raw release-note URLs of every version crossed) and why that description has to go over REST.

Author: manuelleduc

.claude-plugin/marketplace.json

@@ -6,14 +6,14 @@
   },
   "metadata": {
     "description": "Shared LLM (Claude Code) configuration for XWiki org repositories",
-    "version": "1.5.0"
+    "version": "1.5.1"
   },
   "plugins": [
     {
       "name": "xwiki",
       "source": "./xwiki",
       "description": "Org-wide XWiki conventions, MCP servers and dev skills for all xwiki / xwiki-contrib GitHub org repos",
-      "version": "1.5.0",
+      "version": "1.5.1",
       "author": {
         "name": "XWiki Development Team"
       }

kimi.plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "xwiki",
-  "version": "1.5.0",
+  "version": "1.5.1",
   "description": "Org-wide XWiki conventions, MCP servers and dev skills for all xwiki / xwiki-contrib GitHub org repos",
   "interface": {
     "displayName": "XWiki",

opencode.jsonc

@@ -1,6 +1,6 @@
 {
   // XWiki shared LLM configuration for opencode (https://opencode.ai).
-  // version: 1.5.0 — keep in sync with the plugin version (see CLAUDE.md).
+  // version: 1.5.1 — keep in sync with the plugin version (see CLAUDE.md).
   //
   // Paths reference this checkout through the XWIKI_LLM_HOME environment variable so this file is
   // identical for everyone (no personal paths) and works whether it is used globally or per-project.

xwiki/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "xwiki",
   "description": "Org-wide XWiki conventions, MCP servers and dev skills for all xwiki / xwiki-contrib GitHub org repos",
-  "version": "1.5.0",
+  "version": "1.5.1",
   "author": {
     "name": "XWiki Development Team",
     "url": "https://xwiki.org"

xwiki/okf/conventions/commit-messages.md

@@ -36,6 +36,13 @@ The documented format is:
   in any way?"*; if yes, an issue is mandatory. A batch refactoring that changes runtime behaviour
   across many files therefore needs an issue, referenced from every commit of the campaign — not
   `[Misc]`.
+- **Dependency upgrades split on the same test:** a dependency that only ever reaches developers —
+  a `devDependencies`/`peerDependencies` entry, a build or test-scoped Maven dependency — is
+  `[Misc]`; one that ships to users (declared in `dependencies`, or a runtime Maven dependency)
+  needs an issue. Check where the dependency is actually declared before choosing: a shared version
+  catalog (pnpm `catalog:`, a `pom.xml` property) hides that distinction, and the same artifact can
+  be dev-only in one module and runtime in another — one runtime declaration is enough to require
+  the issue.
 
 Issue tracker is https://jira.xwiki.org (NOT GitHub Issues); see [[jira]] for access and the
 issue-field conventions. For the full PR/commit flow (one squashed commit per issue, PR description,

xwiki/okf/servers/jira.md

@@ -53,6 +53,16 @@ correct. Check what the project actually exposes before insisting on a field.
 Write the **description in JIRA wiki markup** (`h2.`, `{{monospace}}`, `*bold*`, `* bullet`) and make
 it explain the **user-visible problem**, not just the code change — but mind the markup gotchas below.
 
+## Dependency-upgrade issues
+
+A dependency upgrade that ships to users needs its own issue (the `[Misc]` split is in
+[[commit-messages]]): summary `Upgrade to <dependency> <version>`, component **Dependency Upgrades**.
+The description is the **raw release-note URLs of every version being crossed** — one line each, from
+the version after the one currently declared up to the target — not just the target's; skipping the
+intermediates hides the changes actually being pulled in. Keep them as bare URLs, which means setting
+the description over REST: `jira-cli` runs a body through its Markdown converter and rewrites a plain
+URL as `[url|url]`.
+
 ## Resolving / closing an issue
 
 Choose the **resolution** that matches reality and **assign the issue to yourself** as you close it