Bring back next tag on sdk publication (#517)

### Proposed Changes
* change 1
* change 2

### Checklist
- [ ] Tests
- [ ] Translations
- [ ] Security Implications Contemplated (add notes if applicable)

### Additional Info
** any additional useful context or info **

### Screenshots
Original             |  Updated
:-------------------------:|:-------------------------:
** original screenshot **  |  ** updated screenshot **

fixes #515

---------

Co-authored-by: Kevin <kfariid@gmail.com>

Author: KevinDavilaDotCMS

.github/actions/core-cicd/deployment/deploy-javascript-sdk/action.yml

@@ -2,16 +2,22 @@
 #
 # VERSIONING (ADR-0019 — date-lockstep versioning):
 # - The SDK version is always the dotCMS release version it ships with. There is no
-#   independent SDK versioning and no `@next` prerelease channel.
+#   independent SDK versioning.
 # - Single source of truth: the `version` input, supplied by the caller (the dotCMS
 #   release pipeline — see cicd_release-sdk.yml, which derives it from the GitHub
 #   Release tag, mirroring how cicd_release-cli.yml versions @dotcms/dotcli).
-# - Every invocation publishes every SDK package at that exact version to the `latest`
-#   npm dist-tag — including releases where the SDK has no code changes, to preserve
-#   the one-dotCMS-version <-> one-SDK-version invariant.
+# - Every real-release invocation publishes every SDK package at that exact version to
+#   the `latest` npm dist-tag — including releases where the SDK has no code changes, to
+#   preserve the one-dotCMS-version <-> one-SDK-version invariant.
+#
+# `next` TAG (internal dev/QA use only):
+# - cicd_3-trunk.yml also calls this action on merges to main that touch SDK files,
+#   passing npm-tag: 'next' and a version computed from the current `latest` plus a
+#   `-next.<run_number>` suffix. This is never a date-lockstep-shaped version and must
+#   never be recommended to customers — see issue #36701.
 #
 name: 'SDK Publish NPM Packages - Stable'
-description: 'Publish the dotCMS SDK libs on NPM registry at the given version.'
+description: 'Publish the dotCMS SDK libs on NPM registry at the given version and dist-tag.'
 inputs:
   ref:
     description: 'Branch/tag to build from'
@@ -20,6 +26,10 @@ inputs:
   version:
     description: 'Exact version to publish every @dotcms/* SDK package at (e.g. 26.7.14-1)'
     required: true
+  npm-tag:
+    description: 'npm dist-tag to publish under (e.g. latest, next)'
+    required: false
+    default: 'latest'
   npm-token:
     description: 'NPM token'
     required: true
@@ -150,10 +160,12 @@ runs:
       env:
         RELEASE_VERSION: ${{ inputs.version }}
         NPM_AUTH_TOKEN: ${{ inputs.npm-token }}
+        NPM_TAG: ${{ inputs.npm-tag }}
       run: |
         set -euo pipefail
         echo "::group::Publishing SDK packages"
         echo "Version: $RELEASE_VERSION"
+        echo "Tag:     $NPM_TAG"
         echo ""
 
         echo "//registry.npmjs.org/:_authToken=${NPM_AUTH_TOKEN}" > ~/.npmrc
@@ -164,8 +176,8 @@ runs:
           echo "📦 Processing @dotcms/${sdk}..."
           cd "$sdk"
 
-          echo "  🚀 Publishing: @dotcms/${sdk}@${RELEASE_VERSION}"
-          if npm publish --access public --tag latest; then
+          echo "  🚀 Publishing: @dotcms/${sdk}@${RELEASE_VERSION} (tag: ${NPM_TAG})"
+          if npm publish --access public --tag "${NPM_TAG}"; then
             echo "  ✅ Published"
           else
             echo "  ❌ Failed to publish"

.github/workflows/cicd_3-trunk.yml

@@ -125,11 +125,86 @@ jobs:
       NPM_ORG_TOKEN: ${{ secrets.NPM_ORG_TOKEN }}
       SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}
 
+  # Publish SDK packages to the `next` npm dist-tag — internal dev/QA use only, never
+  # date-lockstep-shaped, never recommended to customers (see issue #36701). Kept as its
+  # own job (not folded into cicd_comp_deployment-phase.yml) so this trunk-only concern
+  # can't affect nightly/manual/release, which don't opt into it.
+  #
+  # Version = the currently-published `latest` npm version, plus a `-next.<run_number>`
+  # suffix — computed live on every run, no local VERSION file. Gated on the existing
+  # sdk_libs change-detection filter (only publish when SDK files actually changed) and
+  # skipped for manual workflow_dispatch runs.
+  publish-sdk-next:
+    name: Publish SDK (next)
+    needs: [ initialize, test ]
+    # Explicit success check on `test` (not the always()/!failure() idiom used by
+    # sibling jobs) — this job publishes to a real, public npm registry, so it should
+    # require `test` to have actually run and passed, not merely "didn't fail/wasn't
+    # cancelled" (which also admits a skipped test job).
+    if: >-
+      needs.test.result == 'success' &&
+      fromJSON(needs.initialize.outputs.filters).sdk_libs == 'true' &&
+      github.event_name != 'workflow_dispatch'
+    runs-on: ubuntu-${{ vars.UBUNTU_RUNNER_VERSION || '24.04' }}
+    steps:
+      - name: 'Compute next version'
+        id: next-version
+        env:
+          NPM_AUTH_TOKEN: ${{ secrets.NPM_ORG_TOKEN }}
+        run: |
+          set -euo pipefail
+          echo "//registry.npmjs.org/:_authToken=${NPM_AUTH_TOKEN}" > ~/.npmrc
+
+          LATEST_VERSION=$(npm view @dotcms/client version)
+          NEXT_VERSION="${LATEST_VERSION}-next.${{ github.run_number }}"
+
+          echo "::notice:: Currently published latest version: $LATEST_VERSION"
+          echo "::notice:: Publishing next version: $NEXT_VERSION"
+
+          echo "version=$NEXT_VERSION" >> "$GITHUB_OUTPUT"
+
+      - name: 'Publish SDK packages to NPM (next)'
+        id: deploy-javascript-sdk
+        uses: ./.github/actions/core-cicd/deployment/deploy-javascript-sdk
+        with:
+          ref: ${{ github.sha }}
+          version: ${{ steps.next-version.outputs.version }}
+          npm-tag: next
+          npm-token: ${{ secrets.NPM_ORG_TOKEN }}
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: 'Slack Notification (SDK next announcement)'
+        if: success() && steps.deploy-javascript-sdk.outputs.published == 'true'
+        continue-on-error: true
+        uses: ./.github/actions/core-cicd/notification/notify-slack
+        with:
+          channel-id: "log-sdk-libs"
+          payload: |
+            > :large_orange_circle: *Attention dotters:* SDK libs published to `next`!
+            >
+            > This automated script is happy to announce that a new *_SDK libs_* version *tagged as:* [ `${{ steps.next-version.outputs.version }}` ] is now available on the `NPM` registry under the `next` tag :package:. This is an internal dev/QA build, not an official release — do not recommend it to customers.
+            > `npm install @dotcms/client@next`
+            > <${{ github.server_url }}/${{ github.repository }}/commit/${{ github.sha }}|View commit> · <${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}|View workflow run>
+          slack-bot-token: ${{ secrets.SLACK_BOT_TOKEN }}
+
+      - name: 'Slack Notification (SDK next failure)'
+        if: failure()
+        continue-on-error: true
+        uses: ./.github/actions/core-cicd/notification/notify-slack
+        with:
+          channel-id: "log-sdk-libs"
+          payload: |
+            > :red_circle: *SDK `next` publish FAILED!*
+            >
+            > The automated SDK `next` publish failed while trying to publish version `${{ steps.next-version.outputs.version }}`.
+            > <${{ github.server_url }}/${{ github.repository }}/commit/${{ github.sha }}|View commit> · <${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}|View workflow run — check logs for details>
+          slack-bot-token: ${{ secrets.SLACK_BOT_TOKEN }}
+
   # Finalize job - aggregates results from previous jobs
   finalize:
     name: Finalize
     if: always()
-    needs: [ initialize, build, build-cli, test, deployment]
+    needs: [ initialize, build, build-cli, test, deployment, publish-sdk-next ]
     uses: ./.github/workflows/cicd_comp_finalize-phase.yml
     with:
       artifact-run-id: ${{ needs.initialize.outputs.artifact-run-id }}

core-web/libs/sdk/ai/scripts/generate-spec.ts

@@ -58,7 +58,7 @@ const EXCLUDED_PATTERNS = [
 ];
 
 const DEFAULT_SPEC_PATH = '/api/openapi.json';
-const DEFAULT_SPEC_URL = `https://corpsites-headless.dotcms.cloud${DEFAULT_SPEC_PATH}`;
+const DEFAULT_SPEC_URL = `https://dotcms-corp-headless-prod.dotcms.dev${DEFAULT_SPEC_PATH}`;
 
 /**
  * Matches a path against a pattern. Pattern syntax: