Commit bb8a8af
authored
fix(ci): run changeset release as bombshell-bot app (#123)
* fix(ci): run changeset release as bombshell-bot app
The Publish workflow passed the default `secrets.GITHUB_TOKEN` to
`changesets/action`, so the "Version Packages" PR, the version-bump
commit, and the release tag were all attributed to `github-actions[bot]`
instead of our `bombshell-bot` GitHub App like the other Bombshell repos.
Mint an installation token from the org-level `BOT_APP_ID` /
`BOT_PRIVATE_KEY` secrets via `actions/create-github-app-token`, check
out with it so the persisted git credentials push as the app, set the
git user to the app identity so the bump commit is authored by it, and
hand the token to `changesets/action` so it opens the PR as the app.
tty can't reuse `bombshell-dev/automation`'s publish workflow (that one
builds with pnpm/Node; tty builds WASM via make + Deno), so the app-token
pattern is inlined here. `push-with-git-cli: true` stays because the clay
submodule gitlink breaks the GitHub-API push path (0e10dcd), which is
also why the git-user config is needed for commit authorship.
* Apply suggestion from @natemoo-re
* Apply suggestion from @natemoo-re1 parent 0e10dcd commit bb8a8af
1 file changed
Lines changed: 15 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
19 | 19 | | |
20 | 20 | | |
21 | 21 | | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
22 | 29 | | |
23 | 30 | | |
24 | 31 | | |
25 | 32 | | |
26 | 33 | | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
27 | 41 | | |
28 | 42 | | |
29 | 43 | | |
| |||
54 | 68 | | |
55 | 69 | | |
56 | 70 | | |
57 | | - | |
58 | | - | |
| 71 | + | |
0 commit comments