bump: version 0.55.0 → 0.55.1

fix(helm): trigger chart release workflow on helm chart tags
The helm-release workflow was only triggering on v* tags (MCP server releases), not on nextcloud-mcp-server-* tags (helm chart releases). This caused chart releases to be skipped because: 1. Helm chart version bump creates tag nextcloud-mcp-server-X.Y.Z 2. Workflow never runs for this tag (pattern didn't match) 3. Next v* tag triggers workflow at wrong commit (Chart.yaml not updated) 4. chart-releaser skips because version already exists Fix: Add nextcloud-mcp-server-* to workflow trigger pattern so chart releases execute at the correct commit where Chart.yaml has the new version. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-22 20:53:07 +00:00 · 2025-12-22 21:48:26 +01:00
4 changed files with 9 additions and 2 deletions
@@ -4,6 +4,7 @@ on:
  push:
    tags:
      - v*
+      - nextcloud-mcp-server-*

 jobs:
  release:
@@ -1,6 +1,6 @@
 [tool.commitizen]
 name = "cz_conventional_commits"
-version = "0.55.0"
+version = "0.55.1"
 tag_format = "nextcloud-mcp-server-$version"
 version_scheme = "semver"
 update_changelog_on_bump = true
@@ -14,6 +14,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Configurable resource limits
 - Grafana dashboard annotations

+## nextcloud-mcp-server-0.55.1 (2025-12-22)
+
+### Fix
+
+- **helm**: trigger chart release workflow on helm chart tags
+
 ## nextcloud-mcp-server-0.55.0 (2025-12-22)

 ### BREAKING CHANGE
@@ -2,7 +2,7 @@ apiVersion: v2
 name: nextcloud-mcp-server
 description: A Helm chart for Nextcloud MCP Server - enables AI assistants to interact with Nextcloud
 type: application
-version: 0.55.0
+version: 0.55.1
 appVersion: "0.59.0"
 keywords:
  - nextcloud