JJ Kasper
8373776f5e
Revert turborepo to 1.13.3-canary.2 cont. ( #64895 )
...
Continues https://github.com/vercel/next.js/pull/64892 which reverted
original upgrade first before applying the upgrade to version we think
should be clear.
Closes NEXT-3198
2024-04-22 23:40:49 +00:00
JJ Kasper
75c9e2b85e
Revert turborepo to 1.13.3-canary.2 ( #64892 )
...
Reverts turborepo bump while investigating some issues
reverts: https://github.com/vercel/next.js/pull/64767
reverts: https://github.com/vercel/next.js/pull/64842
x-ref: [slack
thread](https://vercel.slack.com/archives/C04KC8A53T7/p1713816363062429 )
Closes NEXT-3195
2024-04-22 21:29:13 +00:00
Tim Neutkens
bd6ab041a4
Upgrade Turborepo ( #64767 )
...
## What?
Upgrade Turborepo to the latest version and enable the new terminal UI
to dogfood: https://turbo.build/blog/turbo-1-13-0#new-terminal-ui .
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
### Adding or Updating Examples
- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas )
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs )
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
Closes NEXT-3164
2024-04-19 18:26:54 +00:00
Sam Ko
7b5d81c0c9
chore: upgrade turbo to 1.12.5 ( #63163 )
2024-03-11 20:35:54 -04:00
Sam Ko
c1bce948e9
chore: upgrade turbo to 1.12.2 ( #61643 )
...
## Changes
- Upgrade turbo from 1.11.3 to 1.12.2
Closes NEXT-2353
2024-02-05 00:03:06 +00:00
JJ Kasper
90ac2df874
Revert "Revert actions/setup-node v4 bump" ( #61640 )
...
This doesn't appear to be the root cause so can re-land
Reverts vercel/next.js#61637
Closes NEXT-2351
2024-02-04 14:06:28 -08:00
JJ Kasper
226824e0d9
Revert actions/setup-node v4 bump ( #61637 )
...
Aims to revert back to previous npm version most likely bumped when this
action was bumped causing our publish to fail
x-ref:
https://github.com/vercel/next.js/actions/runs/7770035719/job/21189787242#step:11:307
Closes NEXT-2350
2024-02-04 19:37:05 +00:00
Leah
1240cda484
chore: update github actions ( #61517 )
...
### 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>
2024-02-01 22:13:29 +01:00
Sam Ko
2d9c01099c
chore: update turbo to the latest ( #60294 )
...
Update :turbo-new: to the latest (v.1.11.3).
Closes NEXT-2004
2024-01-08 11:17:04 -08:00
Balázs Orbán
1ff7f07875
feat: drop Node.js 16 ( #56896 )
...
### What?
BREAKING CHANGE: Bump the minimum required Node.js version.
### Why?
Node.js 16 has reached end-of-life in September.
Bumped to `18.18.2` since it contained some security-related patches: https://nodejs.org/en/blog/vulnerability/october-2023-security-releases
### How?
Bumped `engines` where needed, upgraded the workflows.
This will allow us to remove quite a few polyfills, I'll open separate PRs for those.
2023-10-16 21:41:38 +00:00
Sukka
edb92a30b5
test: speed up isolated next instance test setup ( #56525 )
2023-10-07 00:15:59 +02:00
JJ Kasper
a970f28439
Add code freeze GitHub actions for releasing ( #56325 )
...
Co-authored-by: Steven <steven@ceriously.com>
Co-authored-by: Zack Tanner <zacktanner@gmail.com>
2023-10-02 23:10:40 +02:00
