[linkwarden] Chart Update

[mvprowess]

Version path: 2.5.3 → 2.6.0 → 2.9.0 → 2.10.0 → 2.14.0

Existing Issues:

• fix templating issues and enabling a RollingUpdate deployment strategy as described in [linkwarden] templating issue with kubernetes/helm strategy enabled #37

• add/fix support for NodePort services as described in [linkwarden] NodePort definition is not applied #38

• 2.6.0 added OIDC/Google OAuth and NEXT_PUBLIC_CREDENTIALS_ENABLED

• 2.9.0 added Ollama AI integration env vars

• 2.10.0 added OpenAI/custom AI integration env vars

• 2.14.0 is a security fix release

Changes required (chronological):

• 2.6.0 — Add OIDC/social auth section: NEXT_PUBLIC_CREDENTIALS_ENABLED and Google OAuth vars
• 2.9.0 — Add Ollama AI section: NEXT_PUBLIC_OLLAMA_ENDPOINT_URL, OLLAMA_MODEL
• 2.10.0 — Add OpenAI/custom AI section: OPENAI_API_KEY, OPENAI_MODEL, CUSTOM_OPENAI_BASE_URL, TEXT_CONTENT_LIMIT
• Verify bitnami/postgresql subchart image override is in place (covered by General Changes issue)
• Bump appVersion and image tag to 2.14.0
• Bump chart version to 1.0.0

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

false

[mvprowess]

Landed in #100, chart 0.5.0. Notes on how this differed from the checklist:

• Google/OIDC social auth, Ollama AI tagging, and OpenAI/custom AI provider support don't need dedicated per-provider fields in this chart — it already has a generic ~55-provider SSO mechanism, and the AI-tagging/OpenAI env vars are exposed through a new generic extraEnvVars field added in this pass rather than hand-added dedicated fields (this chart has no config passthrough the way gobackup does, so a handful of new dedicated fields per upstream release isn't sustainable long-term).
• The bitnami/postgresql subchart image override is in place.
• Target ended up at 2.16.2 rather than 2.14.0 — reviewed all 42 releases in the range via the GitHub API rather than stopping at 2.14.0. Confirmed CVE-2026-42455 (stored XSS via archive upload, affects <=2.14.0) is real and that 2.15.0's hardening release is the right fix target.
• Found a critical gap this checklist didn't mention at all: 2.6.1 requires a mandatory one-time migration script for anyone upgrading from 2.6.0 or earlier — which is every existing install of this chart. Documented prominently in the README.
• Also corrected the license annotation from MIT to the actual AGPL-3.0 (same mistake as linkstack), and fixed two real pre-existing bugs unrelated to any of this: the bungie/fusionauth SSO providers had never actually been wired through to the container's environment despite their Secret existing, and configuring more than one SSO provider at once has always broken the chart outright (a Helm whitespace-trim bug).
• The #37/#38 items above (RollingUpdate/templating, NodePort) were not addressed as part of this pass — they were already closed independently (stale/not-planned) before this migration started and weren't revisited here.

Chart version bump to 1.0.0 intentionally left open until this has had some real-world use post-update.