From 2f7cdefc0562f914af22e6cec55730a3208a7642 Mon Sep 17 00:00:00 2001 From: Mauricio Siu Date: Tue, 10 Feb 2026 18:41:20 -0600 Subject: [PATCH] fix: update release tag handling in install script - Enhanced the logic for setting the RELEASE_TAG environment variable based on the VERSION_TAG. - Now supports specific version tags (e.g., v0.26.6) by setting RELEASE_TAG to "latest", while other tags (canary, feature/*) are used as-is. --- apps/website/public/install.sh | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/apps/website/public/install.sh b/apps/website/public/install.sh index 6624c16..1bed881 100644 --- a/apps/website/public/install.sh +++ b/apps/website/public/install.sh @@ -261,7 +261,11 @@ install_dokploy() { # Installation # Set RELEASE_TAG environment variable for canary/feature versions release_tag_env="" - if [ "$VERSION_TAG" != "latest" ]; then + if [[ "$VERSION_TAG" =~ ^v[0-9]+\.[0-9]+\.[0-9]+ ]]; then + # Specific version (v0.26.6, v0.26.7, etc.) → latest + release_tag_env="-e RELEASE_TAG=latest" + elif [ "$VERSION_TAG" != "latest" ]; then + # canary, feature/*, etc. → use the tag as-is release_tag_env="-e RELEASE_TAG=$VERSION_TAG" fi