Skip to content

remove github app use in workflows - #14798

Merged
gr2m merged 6 commits into
mainfrom
remove-github-app-use-in-workflows
Apr 28, 2026
Merged

remove github app use in workflows#14798
gr2m merged 6 commits into
mainfrom
remove-github-app-use-in-workflows

Conversation

@gr2m

@gr2m gr2m commented Apr 28, 2026

Copy link
Copy Markdown
Collaborator
  • ci: remove use of github app authentication
  • ci(auto-merge-release-prs): make it work with any bot

Comment thread .github/workflows/backport.yml
Comment thread .github/workflows/update-model-settings.yml
@gr2m gr2m mentioned this pull request Apr 28, 2026
gr2m added a commit that referenced this pull request Apr 28, 2026
@gr2m gr2m mentioned this pull request Apr 28, 2026
@gr2m
gr2m merged commit 4d276a2 into main Apr 28, 2026
17 checks passed
@gr2m
gr2m deleted the remove-github-app-use-in-workflows branch April 28, 2026 22:30
gr2m added a commit that referenced this pull request Apr 28, 2026
Backports the recent main-branch fixes that re-enabled releases after
the GitHub App was retired and provenance was configured.

## Backported PRs

- #14784 — `ci(release): use \`secrets.GITHUB_TOKEN\``
- #14785 — `ci(release): git config for GITHUB_TOKEN`
- #14787 — `ci(release): sign commits by changesets/acion`
- #14791 — `ci(release): use Node 24`
- #14793 — `build(pkg): set \`repository.url\` to
https://github.com/vercel/ai`
- #14794 — `normalize package json files`
- #14795 — `fix: trigger releases after provenance setup`
- #14798 — `remove github app use in workflows`

## Notes on differences from main

- v6 lacks the `@ai-sdk/otel` and `@ai-sdk/workflow` packages — both
were excluded from the changeset and the package.json normalization
sweep.
- `release.yml` on v6 does not have the snapshot-release path that
exists on main, so only the relevant subset of
#14784/#14785/#14787/#14791 was applied. `NPM_TOKEN:
secrets.NPM_TOKEN_ELEVATED` was kept in v6 since OIDC trusted publishing
has not been configured for v6 packages.
- `auto-merge-release-prs.yml` keeps the existing `GR2M_PR_REVIEW_TOKEN`
(still needed for PR approval); only the `Bot` user-type check from
#14798 was applied.
gr2m added a commit that referenced this pull request Apr 28, 2026
Backports the recent main-branch fixes that re-enabled releases after
the GitHub App was retired and provenance was configured.

## Backported PRs

- #14784 — `ci(release): use \`secrets.GITHUB_TOKEN\``
- #14785 — `ci(release): git config for GITHUB_TOKEN`
- #14787 — `ci(release): sign commits by changesets/acion`
- #14791 — `ci(release): use Node 24`
- #14793 — `build(pkg): set \`repository.url\` to
https://github.com/vercel/ai`
- #14794 — `normalize package json files`
- #14795 — `fix: trigger releases after provenance setup`
- #14798 — `remove github app use in workflows` (the auto-merge bot-type
check + `id-token: write` follow-up)

## Notes on differences from main / v6

- v5 lacks the `@ai-sdk/bytedance`, `@ai-sdk/devtools`,
`@ai-sdk/klingai`, `@ai-sdk/open-responses`, `@ai-sdk/otel`,
`@ai-sdk/voyage`, and `@ai-sdk/workflow` packages — all excluded from
the changeset and the package.json sweep.
- v5 has no `backport.yml` or `update-model-settings.yml` workflows, so
the corresponding parts of #14798 do not apply.
- v5's `release.yml` is simpler than main's (no snapshot path, no
notify-released-PRs step), so only the relevant subset of
#14784/#14785/#14787/#14791 was applied. `NPM_TOKEN:
secrets.NPM_TOKEN_ELEVATED` was kept since OIDC trusted publishing has
not been configured for v5 packages.
- `auto-merge-release-prs.yml` keeps the existing `GR2M_PR_REVIEW_TOKEN`
(still needed for PR approval); only the `Bot` user-type check from
#14798 was applied.
- `permissions` block added to `release.yml` with `id-token: write`,
matching the v6 backport.
gr2m added a commit that referenced this pull request Jun 5, 2026
- **ci: remove use of github app authentication**
- **ci(auto-merge-release-prs): make it work with any bot**
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants