From 0c18e54e7991ec07fdeed6cce94301af7d1dc693 Mon Sep 17 00:00:00 2001 From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com> Date: Wed, 11 Sep 2024 21:35:40 +0100 Subject: [PATCH] Delete the old actions workflow for release-it --- .github/workflows/release.yml | 50 ----------------------------------- 1 file changed, 50 deletions(-) delete mode 100644 .github/workflows/release.yml diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml deleted file mode 100644 index e7632ecdb..000000000 --- a/.github/workflows/release.yml +++ /dev/null @@ -1,50 +0,0 @@ -name: Release - -on: - workflow_dispatch: - inputs: - tag: - required: true - type: string - description: 'Which tag do we want to retry? this should begin with v, and match exactly one of the tags present on the repo' - push: - tags: - - 'v*' - -jobs: - release: - name: 'Tagged Release' - runs-on: 'ubuntu-latest' - - steps: - - uses: actions/checkout@v4 - with: - ref: ${{ github.events.inputs.tag || github.ref }} - - uses: wyvox/action-setup-pnpm@v3 - with: - node-registry-url: "https://registry.npmjs.org" - - run: pnpm build - - # > This is not interactive right? - # correct - # - # > This doesn't bump the version, just publish right? - # correct - # - # > Do we have a way to tell it to ignore already published packages in case we need to re-run the job? - # this is default behavior - # - # > It will skip the private packages, presumably? - # yes - # - # > --force - # Packages are proceeded to be published even if their current version is already in the - # registry. - # - # > --no-git-checks - # we publish from tags, and default behavior is to only allow publishing on main/master - - run: | - npm whoami --registry=https://registry.npmjs.org/ - pnpm -r publish --access public --no-git-checks --force - env: - NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}