From 5b36754a198f95b65637598dfcfab5528ccfc949 Mon Sep 17 00:00:00 2001 From: Lex Christopherson Date: Wed, 18 Mar 2026 10:45:39 -0600 Subject: [PATCH] fix(ci): remove @latest npm promotion from pipeline MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Dev-stamped versions (2.28.0-dev.xxx) should never be promoted to @latest on npm. Stable releases are handled by the publish-version workflow. The pipeline promotes @dev → @next only. Co-Authored-By: Claude Opus 4.6 (1M context) --- .github/workflows/pipeline.yml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/.github/workflows/pipeline.yml b/.github/workflows/pipeline.yml index 292017938..617e48eb8 100644 --- a/.github/workflows/pipeline.yml +++ b/.github/workflows/pipeline.yml @@ -137,10 +137,8 @@ jobs: OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }} GSD_LIVE_TESTS: "1" - - name: Promote to @latest - run: npm dist-tag add gsd-pi@${{ needs.dev-publish.outputs.dev-version }} latest - env: - NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} + # NOTE: @latest promotion is handled by the publish-version workflow, + # not by the pipeline. Dev versions should never be tagged as @latest. - name: Log in to GHCR uses: docker/login-action@v3