bump: version 0.55.1 → 0.55.2

fix(helm): set OIDC client env vars when using existingSecret
The deployment template only checked for clientId being set in values.yaml, so when using existingSecret without setting clientId, the NEXTCLOUD_OIDC_CLIENT_ID and NEXTCLOUD_OIDC_CLIENT_SECRET env vars were never created. This broke existingSecret for OIDC-based auth - the server would always fall back to DCR even when pre-registered credentials were provided via secret. Fix: Check for EITHER clientId OR existingSecret being set before creating the OIDC client credential env vars. Affects both OIDC-based auth modes: - auth.oauth.existingSecret (OAuth mode) - auth.multiUserBasic.existingSecret (multi-user BasicAuth with offline access) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-22 21:21:45 +00:00 · 2025-12-22 22:21:23 +01:00 · 2025-12-22 20:53:07 +00:00 · 2025-12-22 21:48:26 +01:00
5 changed files with 17 additions and 4 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.2"
 tag_format = "nextcloud-mcp-server-$version"
 version_scheme = "semver"
 update_changelog_on_bump = true
@@ -14,6 +14,18 @@ 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.2 (2025-12-22)
 ### Fix
 - **helm**: set OIDC client env vars when using existingSecret
 ## 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.2
 appVersion: "0.59.0"
 keywords:
  - nextcloud
@@ -100,7 +100,7 @@ spec:
                  key: {{ .Values.auth.multiUserBasic.tokenEncryptionKeyKey }}
            - name: NEXTCLOUD_OIDC_SCOPES
              value: {{ .Values.auth.multiUserBasic.scopes | quote }}
-            {{- if .Values.auth.multiUserBasic.clientId }}
+            {{- if or .Values.auth.multiUserBasic.clientId .Values.auth.multiUserBasic.existingSecret }}
            # Static OAuth credentials (optional - uses DCR if not provided)
            - name: NEXTCLOUD_OIDC_CLIENT_ID
              valueFrom:
@@ -122,7 +122,7 @@ spec:
              value: {{ include "nextcloud-mcp-server.publicIssuerUrl" . | quote }}
            - name: NEXTCLOUD_OIDC_SCOPES
              value: {{ .Values.auth.oauth.scopes | quote }}
-            {{- if .Values.auth.oauth.clientId }}
+            {{- if or .Values.auth.oauth.clientId .Values.auth.oauth.existingSecret }}
            - name: NEXTCLOUD_OIDC_CLIENT_ID
              valueFrom:
                secretKeyRef:
Author	SHA1	Message	Date
github-actions[bot]	6e2be579e0	bump: version 0.55.1 → 0.55.2	2025-12-22 21:21:45 +00:00
Chris Coutinho	8ba3ae73ab	fix(helm): set OIDC client env vars when using existingSecret The deployment template only checked for clientId being set in values.yaml, so when using existingSecret without setting clientId, the NEXTCLOUD_OIDC_CLIENT_ID and NEXTCLOUD_OIDC_CLIENT_SECRET env vars were never created. This broke existingSecret for OIDC-based auth - the server would always fall back to DCR even when pre-registered credentials were provided via secret. Fix: Check for EITHER clientId OR existingSecret being set before creating the OIDC client credential env vars. Affects both OIDC-based auth modes: - auth.oauth.existingSecret (OAuth mode) - auth.multiUserBasic.existingSecret (multi-user BasicAuth with offline access) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2025-12-22 22:21:23 +01:00
github-actions[bot]	dbf3d5ec10	bump: version 0.55.0 → 0.55.1	2025-12-22 20:53:07 +00:00
Chris Coutinho	5b9e76ddb4	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 21:48:26 +01:00