1240cda484
### Why? They used the `node16` runner which is deprecated ### Notable breaking changes #### `dessant/lock-threads@v5` [link](https://github.com/dessant/lock-threads) Now also locks discussions (in addition to issues and pull requests): https://github.com/dessant/lock-threads/blob/main/CHANGELOG.md#500-2023-11-14 #### `actions/stale@v9` [link](https://github.com/actions/stale) Is now stateful: If the action ends because of [operations-per-run](https://github.com/actions/stale#operations-per-run) then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). https://github.com/actions/stale/releases/tag/v9.0.0 Closes PACK-2347 Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
31 lines
1.2 KiB
YAML
31 lines
1.2 KiB
YAML
# A workflow runs when a release is published, dispatches a new event to the vercel/turbo
|
|
# to notify its release. Turbopack, and other integration workflow will subscribe to this event.
|
|
name: Notify new Next.js release
|
|
on:
|
|
release:
|
|
types: [published]
|
|
|
|
jobs:
|
|
notify:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/github-script@v7
|
|
id: notify-new-release
|
|
with:
|
|
result-encoding: string
|
|
retries: 3
|
|
retry-exempt-status-codes: 400,401
|
|
# Default github token cannot dispath events to the remote repo, it should be
|
|
# a PAT with access to contenst:read&write + metadata:read.
|
|
github-token: ${{ secrets.TURBOPACK_TEST_TOKEN }}
|
|
# Note `event_type` and `client_payload` are contract between vercel/turbo,
|
|
# if these need to be changed both side should be updated accordingly.
|
|
script: |
|
|
github.request('POST /repos/{owner}/{repo}/dispatches', {
|
|
owner: 'vercel',
|
|
repo: 'turbo',
|
|
event_type: 'nextjs-release-published',
|
|
client_payload: {
|
|
version: context.ref
|
|
}
|
|
})
|