From ff9b2f6ab5756fb60e0fe3f8a7e57b598b9577ad Mon Sep 17 00:00:00 2001
From: tastybento <tastybento@users.noreply.github.com>
Date: Fri, 7 Aug 2026 21:26:26 -0700
Subject: [PATCH] The release profile matches the branch we actually release
 from

The profile that strips -SNAPSHOT activated on origin/master, inherited from
the older addons. This repo releases from main, so it never fired and every
Jenkins build - including main - shipped a SNAPSHOT.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014as2obVi1QJj8CRTSqXBRr
---
 pom.xml | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/pom.xml b/pom.xml
index a904128..f9f8321 100644
--- a/pom.xml
+++ b/pom.xml
@@ -78,12 +78,17 @@
                 <build.number>-b${env.BUILD_NUMBER}</build.number>
             </properties>
         </profile>
+        <!-- Release profile: fires only when Jenkins builds the release branch,
+             stripping the -SNAPSHOT and the -bNNN build number so the artifact is
+             just ${build.version}. The older addons match `origin/master`; this
+             repo's release branch is `main`, so the value has to match that or
+             every build stays a SNAPSHOT. -->
         <profile>
-            <id>master</id>
+            <id>main</id>
             <activation>
                 <property>
                     <name>env.GIT_BRANCH</name>
-                    <value>origin/master</value>
+                    <value>origin/main</value>
                 </property>
             </activation>
             <properties>