update.yml

"on":
  schedule:
    - cron: 5 4 * * *
  workflow_dispatch: {}
name: Update
jobs:
  update:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
      - uses: actions/setup-node@v4
        with:
          node-version: 18
          cache: npm
      - run: git checkout fixtures-update || true
      - run: npm ci
      - run: node bin/record --update
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          FIXTURES_USER_A_TOKEN_FULL_ACCESS: ${{ secrets.FIXTURES_USER_A_TOKEN_FULL_ACCESS }}
          FIXTURES_USER_B_TOKEN_FULL_ACCESS: ${{ secrets.FIXTURES_USER_B_TOKEN_FULL_ACCESS }}
      - name: create pull request
        uses: gr2m/create-or-update-pull-request-action@v1.x
        env:
          GITHUB_TOKEN: ${{ secrets.OCTOKITBOT_PAT }}
        with:
          title: 🚧 🤖📯 Fixtures changed
          body: >
            I found new changes in the recorded fixtures 👋🤖


            I can't tell if the changes are fixes, features or breaking, you'll
            have to figure that out on yourself and adapt the commit messages
            accordingly to trigger the right release, see [our commit message
            conventions](https://github.com/octokit/openapi/blob/main/CONTRIBUTING.md#merging-the-pull-request--releasing-a-new-version).
          branch: fixtures-update
          author: Octokit Bot <octokitbot@martynus.net>
          commit-message: "WIP: fixtures changed - please review"
          labels: "Type: Maintenance"