From a8c16d858e3d93deac74bc820cb7e3f17d30a303 Mon Sep 17 00:00:00 2001 From: mintaka Date: Fri, 21 Aug 2026 18:07:19 -0400 Subject: [PATCH] ci: remove stale upstream publish.yml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The original upstream (andi23rosca) semantic-release publish workflow triggers on every push to main and now hard-fails at setup: pnpm/action-setup@v2 with `version: latest` resolves pnpm 11.x, which requires Node >= 22.13, while the workflow pins actions/setup-node@v3 to node 18. Every push to main therefore shows a red `Publish` check. The workflow is a stale artifact: it runs `npx semantic-release` against the old upstream config and could never publish the scoped `@rigelbuild/solid-markdown` package. It is not a required status context (the main ruleset gates on `CI` only), so the failure is cosmetic — but it reddens main on every push. The RIG-2187 react-markdown-10 fork PR supplies the replacement: a tag-driven, dist-tag-aware scoped publish workflow. Delete the stale one now so main is green; the replacement lands with that PR. Refs RIG-2187 Co-authored-by: Matt Wilkinson --- .github/workflows/publish.yml | 33 --------------------------------- 1 file changed, 33 deletions(-) delete mode 100644 .github/workflows/publish.yml diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml deleted file mode 100644 index a2d773a..0000000 --- a/.github/workflows/publish.yml +++ /dev/null @@ -1,33 +0,0 @@ -name: Publish - -permissions: - contents: write - issues: write - pull-requests: write - -on: - push: - branches: - - "main" - -jobs: - publish: - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v3 - - uses: pnpm/action-setup@v2 - with: - version: latest - - uses: actions/setup-node@v3 - with: - node-version: 18 - cache: 'pnpm' - - run: pnpm i - - run: pnpm lint - - run: pnpm build - - - run: npx semantic-release - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - NPM_TOKEN: ${{ secrets.NPM_TOKEN }} - HUSKY: 0