atty/.github/workflows/release-please.yml at master · fentas/atty · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
name: release-please

on:
  push:
    branches: [main, master]

permissions:
  contents: write
  pull-requests: write

# Avoid racing the per-push CI run; release-please is fast but should
# never collide with itself.
concurrency:
  group: release-please
  cancel-in-progress: false

jobs:
  release-please:
    name: maintain release PR
    runs-on: ubuntu-24.04
    steps:
      - uses: actions/checkout@v6
        with:
          fetch-depth: 0

      # The action reads commits since the last release and:
      #   • opens (or updates) a "chore(release): X.Y.Z" PR
      #   • on merge of that PR, creates the vX.Y.Z tag.
      #
      # Authenticating via BUYO_BOT_TOKEN (a PAT under
      # github.com/buyo-bot) instead of GITHUB_TOKEN is the load-
      # bearing change. Tag pushes authenticated with the default
      # GITHUB_TOKEN do NOT trigger downstream workflows — a
      # documented GitHub Actions safety mechanism. With the PAT,
      # the tag push fires `.github/workflows/release.yml` which
      # cross-compiles musl binaries + the multi-arch Docker image.
      #
      # If BUYO_BOT_TOKEN is missing or expires, this job won't be
      # able to push the tag and the release pipeline stalls;
      # re-rotate the PAT under buyo-bot and re-add it to the repo
      # secrets.
      - uses: googleapis/release-please-action@v5
        with:
          token: ${{ secrets.BUYO_BOT_TOKEN }}
          config-file: release-please-config.json
          manifest-file: .release-please-manifest.json