plugin-updating

Plugin Updating

Handles plugin version management for the Shopware AI Coding Tools marketplace.

Template synchronization for templates/plugin-setup/ and shared shell scripts is covered by .claude/rules/template-sync.md, which activates automatically when a template or consumer file is touched.

Plugin Inventory

Current plugin names and versions:

for f in plugins/*/.claude-plugin/plugin.json; do
  name=$(basename "$(dirname "$(dirname "$f")")")
  ver=$(jq -r .version "$f" 2>/dev/null)
  printf '%s: %s\n' "$name" "$ver"
done

Version Bump

When updating a plugin's version:

Step 1: Identify the plugin

Match the plugin name from the user's request against the names listed above. If the name does not appear there, stop and ask the user which plugin they mean.

Step 2: Determine version bump level

If the user specifies a target version, use it. Otherwise, reason about the changes to determine MAJOR, MINOR, or PATCH.

Core question: "Can users do something they could not do before?"

MAJOR — Consumer behavior must change to keep working
  Plugin renamed or extracted
  Skill invocation model changed
  MCP tool surface rewritten
  Agent names/roles replaced
  Config files require migration

MINOR — New user-facing capability added
  New skill, MCP tool, hook type, agent, command, or environment
  Significant new parameters on existing tools
  New independently-queryable test rule

PATCH — Everything else
  Bug fixes, refinements, internal refactoring
  Description/docs improvements
  Validation/guard additions to existing features
  Removing deprecated internals

Watch for these traps:

• "Added" does not always mean MINOR — adding validation to an existing feature is PATCH (same capability, better quality)
• "Breaking" in a description does not always mean MAJOR — if the orchestrator absorbs the change transparently, consumers are unaffected
• Batch additions that individually seem incremental can collectively warrant MINOR when they form a cohesive new capability