Benjamin Woodruff and GitHub
0dc354b8d7
chore: Upgrade to pnpm 10.x ( #92283 )
...
This will let us potentially use https://pnpm.io/settings#minimumreleaseage
2026-04-06 18:12:50 -07:00
Sam Ko and GitHub
3fbffe1d1e
chore: bump pnpm to 9.6.0 ( #68044 )
...
## Why?
- More support for [catalogs](https://pnpm.io/catalogs ) (read
[changelog](https://github.com/pnpm/pnpm/releases ) for more info).
- Successful
[build-and-deploy](https://github.com/vercel/next.js/actions/runs/10127840891 )
run
2024-07-28 04:18:36 -07:00
Sam Ko and GitHub
2a43b5153c
chore: bump pnpm to 9.5.0 ( #67555 )
...
## Why?
Upgrading to [9.5.0](https://github.com/pnpm/pnpm/releases/tag/v9.5.0 )
allows us to start using [catalogs](https://pnpm.io/catalogs ).
2024-07-08 05:13:17 -07:00
Sam Ko and GitHub
e6983b911b
chore: update pnpm to 9.4.0 ( #64945 )
...
## Why?
Notable change of v9 is Corepack is enabled by default.
So we can ensure all package manage/resolved exact same version of pnpm.
- [**v9.0.0**](https://github.com/pnpm/pnpm/releases/tag/v9.0.0 ):
Discontinued support for Node.js v16 and introduced Corepack
compatibility checks. New configuration updates include enabling
`dedupe-injected-deps` and changing the lockfile to version 9, with
better readability and resistance to Git conflicts.
...
- [**v9.4.0**](https://github.com/pnpm/pnpm/releases/tag/v9.4.0 )
- Kudos to @ryota-murakami for the original :pr:! →
https://github.com/vercel/next.js/pull/64854
## Changes
- https://pnpm.io/npmrc#link-workspace-packages defaults to `false` now,
so setting it to `true`
Closes NEXT-3211
2024-06-28 04:41:35 -07:00
Sam Ko and GitHub
e296846427
chore: bump turbo to 2.0.3 ( #66784 )
...
## Why?
This pull request bumps turborepo from 1.13.3-canary.2 to
[2.0.3](https://github.com/vercel/turbo/releases/tag/v2.0.3 ) across
multiple GitHub workflows and configuration files.
Re-attempting after we
[reverted](https://github.com/vercel/next.js/pull/66775 ).
2024-06-12 19:31:42 +00:00
JJ Kasper and GitHub
d22da49b49
Revert "chore: bump turbo to 2.0.3" ( #66775 )
...
Seems the latest turbo version is causing issues with our rust
compilation so reverting for now
Reverts vercel/next.js#66762
2024-06-11 18:17:06 -07:00
Sam Ko and GitHub
561dcf6c43
chore: bump turbo to 2.0.3 ( #66762 )
...
## Why?
This pull request bumps turborepo from 1.13.3-canary.2 to
[2.0.3](https://github.com/vercel/turbo/releases/tag/v2.0.3 ) across
multiple GitHub workflows and configuration files.
2024-06-11 22:28:01 +00:00
Tobias Koppers and GitHub
15980a66d4
remove --turbo, use --experimental-turbo as --turbo ( #55063 )
...
### What?
Switch the default for `--turbo` to the new `--experimental-turbo`, remove the old code in next.js
### Why?
The new approach will be used in future
Closes WEB-1506
2023-09-06 17:46:54 +00:00
JJ Kasper and GitHub
a3ab542630
Add new build and test workflow ( #50436 )
...
This adds new `build and test` and `build and deploy` workflows in favor
of the existing massive `build, test, and deploy` workflow. Since the
new workflows will use `pull_request_target` this waits to remove the
existing workflow until the new one is tested.
While testing this new workflow flakey behavior in tests have also been
addressed. Along with the new workflow we will also be leveraging new
runners which allow us to run tests against the production binary of
`next-swc` so this avoids slight differences in tests we've seen due to
running against the dev binary.
Furthermore we will have a new flow for allowing workflow runs on PRs
from external forks which will either require a comment be checking a
box approving the run after each change or a label added by the team.
The new flow also no longer relies on `actions/cache` or similar which
have proven to be pretty unreliable.
Tests runs with the new workflow can be seen here
https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-27 21:02:31 -07:00
JJ Kasper and GitHub
ec7609e288
Avoid turbo cache miss on root package change ( #43309 )
...
Since the `next-swc` package doesn't rely on any of the root
dependencies this normalizes the `package.json` to avoid cache misses
when the file changes.
x-ref:
https://github.com/vercel/next.js/actions/runs/3535337836/jobs/5933336967
x-ref:
https://github.com/vercel/next.js/actions/runs/3535337836/jobs/5933338363
x-ref: [slack
thread](https://vercel.slack.com/archives/C02HEJASXGD/p1669236151437999 )
2022-11-23 15:32:35 -08:00
JJ Kasper and GitHub
ea9c5aac5f
Update caching for swc turbo builds ( #42929 )
...
Updates to leverage turbo remote caching for the swc builds and
normalize the package versions to prevent repo version bumps from
un-necessarily invalidating the cache.
Full cache hits can be seen in this test run
https://github.com/vercel/next.js/actions/runs/3469932131/jobs/5797559609
2022-11-15 08:24:04 -08:00
