prerelease.yml

name: Prelease

on:
  pull_request:
    types: [labeled, unlabeled, opened, reopened, synchronize]

concurrency: prerelease-${{ github.ref }}

env:
  NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

jobs:
  prelease_inngest:
    runs-on: ubuntu-latest
    permissions:
      contents: write
      id-token: write
    defaults:
      run:
        working-directory: packages/inngest
    if: contains(github.event.pull_request.labels.*.name, 'prerelease/inngest')
    steps:
      - uses: actions/checkout@v3
        with:
          persist-credentials: false

      - uses: ./.github/actions/setup-and-build

      - name: Prerelease PR
        run: node ../../scripts/release/prerelease.js
        env:
          TAG: pr-${{ github.event.pull_request.number }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
          NODE_ENV: test # disable npm access checks; they don't work in CI
          DIST_DIR: dist

      - name: Update PR with latest prerelease
        uses: edumserrano/find-create-or-update-comment@v1
        with:
          token: ${{ secrets.CHANGESET_GITHUB_TOKEN }}
          issue-number: ${{ github.event.pull_request.number }}
          body-includes: '<!-- pr-prerelease-comment-inngest -->'
          comment-author: 'inngest-release-bot'
          body: | # can be a single value or you can compose text with multi-line values
            <!-- pr-prerelease-comment-inngest -->
            A user has added the <kbd>[prerelease/inngest](https://github.com/inngest/inngest-js/labels/prerelease%2Finngest)</kbd> label, so this PR will be published to npm with the tag `pr-${{ github.event.pull_request.number }}`. It will be updated with the latest changes as you push commits to this PR.

            You can install this prerelease version with:

            ```sh
            npm install inngest@pr-${{ github.event.pull_request.number }}
            ```

            The last release was built and published from ${{ github.event.pull_request.head.sha }}.
          edit-mode: replace

  prerelease_eslint-plugin:
    runs-on: ubuntu-latest
    permissions:
      contents: write
      id-token: write
    defaults:
      run:
        working-directory: packages/eslint-plugin
    if: contains(github.event.pull_request.labels.*.name, 'prerelease/eslint-plugin')
    steps:
      - uses: actions/checkout@v3
        with:
          persist-credentials: false

      - uses: ./.github/actions/setup-and-build
        with:
          install-dependencies: false
          build: false

      - run: pnpm install

      - run: pnpm build

      - name: Prerelease PR
        run: node ../../scripts/release/prerelease.js
        env:
          TAG: pr-${{ github.event.pull_request.number }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
          NODE_ENV: test # disable npm access checks; they don't work in CI

      - name: Update PR with latest prerelease
        uses: edumserrano/find-create-or-update-comment@v1
        with:
          token: ${{ secrets.CHANGESET_GITHUB_TOKEN }}
          issue-number: ${{ github.event.pull_request.number }}
          body-includes: '<!-- pr-prerelease-comment-eslint-plugin -->'
          comment-author: 'inngest-release-bot'
          body: | # can be a single value or you can compose text with multi-line values
            <!-- pr-prerelease-comment-eslint-plugin -->
            A user has added the <kbd>[prerelease/eslint-plugin](https://github.com/inngest/inngest-js/labels/prerelease%2Feslint-plugin)</kbd> label, so this PR will be published to npm with the tag `pr-${{ github.event.pull_request.number }}`. It will be updated with the latest changes as you push commits to this PR.

            You can install this prerelease version with:

            ```sh
            npm install @inngest/eslint-plugin@pr-${{ github.event.pull_request.number }}
            ```

            The last release was built and published from ${{ github.event.pull_request.head.sha }}.
          edit-mode: replace

  prerelease_middleware-sentry:
    runs-on: ubuntu-latest
    permissions:
      contents: write
      id-token: write
    defaults:
      run:
        working-directory: packages/middleware-sentry
    if: contains(github.event.pull_request.labels.*.name, 'prerelease/middleware-sentry')
    steps:
      - uses: actions/checkout@v3
        with:
          persist-credentials: false

      - uses: ./.github/actions/setup-and-build
        with:
          install-dependencies: false
          build: false

      - run: pnpm install

      - run: pnpm build

      - name: Prerelease PR
        run: node ../../scripts/release/prerelease.js
        env:
          TAG: pr-${{ github.event.pull_request.number }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
          NODE_ENV: test # disable npm access checks; they don't work in CI

      - name: Update PR with latest prerelease
        uses: edumserrano/find-create-or-update-comment@v1
        with:
          token: ${{ secrets.CHANGESET_GITHUB_TOKEN }}
          issue-number: ${{ github.event.pull_request.number }}
          body-includes: "<!-- pr-prerelease-comment-middleware-sentry -->"
          comment-author: "inngest-release-bot"
          body:
            | # can be a single value or you can compose text with multi-line values
            <!-- pr-prerelease-comment-middleware-sentry -->
            A user has added the <kbd>[prerelease/middleware-sentry](https://github.com/inngest/inngest-js/labels/prerelease%2Fmiddleware-sentry)</kbd> label, so this PR will be published to npm with the tag `pr-${{ github.event.pull_request.number }}`. It will be updated with the latest changes as you push commits to this PR.

            You can install this prerelease version with:

            ```sh
            npm install @inngest/middleware-sentry@pr-${{ github.event.pull_request.number }}
            ```

            The last release was built and published from ${{ github.event.pull_request.head.sha }}.
          edit-mode: replace

  prerelease_middleware-encryption:
    runs-on: ubuntu-latest
    permissions:
      contents: write
      id-token: write
    defaults:
      run:
        working-directory: packages/middleware-encryption
    if: contains(github.event.pull_request.labels.*.name, 'prerelease/middleware-encryption')
    steps:
      - uses: actions/checkout@v3
        with:
          persist-credentials: false

      - uses: ./.github/actions/setup-and-build
        with:
          install-dependencies: false
          build: false

      - run: pnpm install

      - run: pnpm build

      - name: Prerelease PR
        run: node ../../scripts/release/prerelease.js
        env:
          TAG: pr-${{ github.event.pull_request.number }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
          NODE_ENV: test # disable npm access checks; they don't work in CI
          DIST_DIR: dist

      - name: Update PR with latest prerelease
        uses: edumserrano/find-create-or-update-comment@v1
        with:
          token: ${{ secrets.CHANGESET_GITHUB_TOKEN }}
          issue-number: ${{ github.event.pull_request.number }}
          body-includes: "<!-- pr-prerelease-comment-middleware-encryption -->"
          comment-author: "inngest-release-bot"
          body:
            | # can be a single value or you can compose text with multi-line values
            <!-- pr-prerelease-comment-middleware-encryption -->
            A user has added the <kbd>[prerelease/middleware-encryption](https://github.com/inngest/inngest-js/labels/prerelease%2Fmiddleware-encryption)</kbd> label, so this PR will be published to npm with the tag `pr-${{ github.event.pull_request.number }}`. It will be updated with the latest changes as you push commits to this PR.

            You can install this prerelease version with:

            ```sh
            npm install @inngest/middleware-encryption@pr-${{ github.event.pull_request.number }}
            ```

            The last release was built and published from ${{ github.event.pull_request.head.sha }}.
          edit-mode: replace

  prerelease_test:
    runs-on: ubuntu-latest
    permissions:
      contents: write
      id-token: write
    defaults:
      run:
        working-directory: packages/test
    if: contains(github.event.pull_request.labels.*.name, 'prerelease/test')
    steps:
      - uses: actions/checkout@v3
        with:
          persist-credentials: false

      - uses: ./.github/actions/setup-and-build
        with:
          install-dependencies: false
          build: false

      - run: pnpm install

      - run: pnpm build

      - name: Prerelease PR
        run: node ../../scripts/release/prerelease.js
        env:
          TAG: pr-${{ github.event.pull_request.number }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
          NODE_ENV: test # disable npm access checks; they don't work in CI
          DIST_DIR: dist

      - name: Update PR with latest prerelease
        uses: edumserrano/find-create-or-update-comment@v1
        with:
          token: ${{ secrets.CHANGESET_GITHUB_TOKEN }}
          issue-number: ${{ github.event.pull_request.number }}
          body-includes: "<!-- pr-prerelease-comment-test -->"
          comment-author: "inngest-release-bot"
          body:
            | # can be a single value or you can compose text with multi-line values
            <!-- pr-prerelease-comment-test -->
            A user has added the <kbd>[prerelease/test](https://github.com/inngest/inngest-js/labels/prerelease%2Ftest)</kbd> label, so this PR will be published to npm with the tag `pr-${{ github.event.pull_request.number }}`. It will be updated with the latest changes as you push commits to this PR.

            You can install this prerelease version with:

            ```sh
            npm install @inngest/test@pr-${{ github.event.pull_request.number }}
            ```

            The last release was built and published from ${{ github.event.pull_request.head.sha }}.
          edit-mode: replace