vercel__next.js

skills/vercel__next.js

Fork 0

mirror of https://github.com/vercel/next.js.git synced 2026-09-20 02:25:18 +08:00

Commit Graph

Author SHA1 Message Date

Author	SHA1	Message	Date
Benjamin Woodruff	0a355571a0	[ci] Update all actions/* dependencies (#94174 ) Previously we pinned all of these to their current versions at the time. That meant that some of these got pinned to really old versions. This updates all of the "first-party" `actions/` dependencies. Prompted claude with: ``` For all of these uses of actions/, make sure we're pulling in the latest stable version (check the gh cli). When upgrading across major versions, fetch the release notes from the GH releases using the gh CLI and make sure that there are no problems that the upgrade will cause. ``` Claude read all the release notes and seems to think these upgrades are safe. ![Screenshot 2026-05-27 at 3.36.15 PM.png](https://app.graphite.com/user-attachments/assets/4b863905-a983-43a1-ba3d-5d3cc2988bc2.png)	2026-05-28 09:26:57 -07:00
Benjamin Woodruff	4e6331397d	[ci] Also pin first-party GH actions (#93609 ) We were already pinning nearly all of our third-party GitHub actions, but this also pins our first-party ones (things starting with `actions/*`. This gets us closer to being able to enforcing pinning at the repository level: ![Screenshot 2026-05-06 at 4.39.46 PM.png](https://app.graphite.com/user-attachments/assets/ced0b3f2-7de8-4a9a-aa79-8d3efa74197d.png) The one remaining blocker is this self-reference in a `pull_request_target` action: https://github.com/vercel/next.js/blob/c06d94ba22d0156e8bff28c81f7874b73d80ed03/.github/workflows/pull_request_auto_label.yml#L65 I'm still figuring out the best approach to do there, and I'll submit that in a separate PR. Discussion here about enforcing this org-wide: https://vercel.slack.com/archives/C0AM84PRSGL/p1778110550384279	2026-05-08 20:10:55 +00:00
Sebastian "Sebbie" Silbermann	5c165904c1	[ci] Automatically start React sync when new `react@experimental` is available (#93235 )	2026-04-27 08:16:22 +02:00

Benjamin Woodruff

0a355571a0

[ci] Update all actions/* dependencies (#94174 )

Previously we pinned all of these to their current versions at the time.
That meant that some of these got pinned to really old versions. This
updates all of the "first-party" `actions/*` dependencies.

Prompted claude with:

```
For all of these uses of actions/*, make sure we're pulling in the latest stable version (check the gh cli). When upgrading across major versions, fetch the release notes from the GH releases using the gh CLI and make sure that there are no problems that the upgrade will cause.
```

Claude read all the release notes and seems to think these upgrades are
safe.

![Screenshot 2026-05-27 at
3.36.15 PM.png](https://app.graphite.com/user-attachments/assets/4b863905-a983-43a1-ba3d-5d3cc2988bc2.png)

2026-05-28 09:26:57 -07:00

Benjamin Woodruff

4e6331397d

[ci] Also pin first-party GH actions (#93609 )

We were already pinning nearly all of our third-party GitHub actions,
but this also pins our first-party ones (things starting with
`actions/*`.

This gets us closer to being able to enforcing pinning at the repository
level:
![Screenshot 2026-05-06 at
4.39.46 PM.png](https://app.graphite.com/user-attachments/assets/ced0b3f2-7de8-4a9a-aa79-8d3efa74197d.png)

The one remaining blocker is this self-reference in a
`pull_request_target` action:
https://github.com/vercel/next.js/blob/c06d94ba22d0156e8bff28c81f7874b73d80ed03/.github/workflows/pull_request_auto_label.yml#L65

I'm still figuring out the best approach to do there, and I'll submit
that in a separate PR.

Discussion here about enforcing this org-wide:
https://vercel.slack.com/archives/C0AM84PRSGL/p1778110550384279

2026-05-08 20:10:55 +00:00

Sebastian "Sebbie" Silbermann 5c165904c1 [ci] Automatically start React sync when new react@experimental is available (#93235 ) 2026-04-27 08:16:22 +02:00

3 Commits