rsnext/errors/version-staleness.mdx
Balázs Orbán 0f07cf5798
chore: verify missing/invalid/private reproduction links (#54724)
### What?

This PR adds a new action that verifies if the reproduction link is correct _after_ the issue has been created. If it is not, we close the issue and comment on it with the correct steps to take. Check out the [rendered comment here](https://github.com/balazsorban44/next.js/blob/chore/gh-invalid-link-checker/.github/actions/issue-validator/repro-link/invalid-link.md).

Additionally, this PR also does some refactoring to simplify our GitHub actions related to issues.

Tests:

Issue that was supposed to be closed:
 - https://github.com/balazsorban44/next.js/issues/48
   - Issue comment: https://github.com/balazsorban44/next.js/issues/48#issuecomment-1698836121 
   - Issue opened action: https://github.com/balazsorban44/next.js/actions/runs/6023209630
   - Issue labeled action: https://github.com/balazsorban44/next.js/actions/runs/6023209629

Issue that was not supposed to be closed (closed manually afterward):
 - https://github.com/balazsorban44/next.js/issues/49
   - Issue opened action: https://github.com/balazsorban44/next.js/actions/runs/6023214256
   - Issue labeled action: https://github.com/balazsorban44/next.js/actions/runs/6023214258


### Why?

Unfortunately, GitHub is currently missing the [functionality to require a valid reproduction link](https://github.com/orgs/community/discussions/10227) in issue templates. Even if that was supported, this PR adds functionality that could not be covered with a regex validation. Namely, we check if the reproduction is a private repo or not, and potentially could also check the structure to see if it's an actual Next.js project.

### How?

If the link is not in the expected section, not a GitHub, CodeSandbox, or Replay.io link, or does not return an OK response (eg.: private repo/sandbox), the issue is closed/commented.

Related:
- https://github.com/orgs/community/discussions/4629
- https://github.com/orgs/community/discussions/10227

Co-authored-by: Steven <229881+styfle@users.noreply.github.com>
2023-08-30 17:40:57 +00:00

63 lines
1.9 KiB
Text

---
title: Version Staleness
---
## Why This Error Occurred
In the error overlay, a message was shown that the detected Next.js version was out-of-date.
To get the newest features and bug fixes, it is recommended to stay up to date.
## Possible Ways to Fix It
If you are testing out a canary release, upgrade Next.js with one of the following:
```bash filename="Terminal"
npm i next@canary
```
```bash filename="Terminal"
yarn add next@canary
```
```bash filename="Terminal"
pnpm add next@canary
```
```bash filename="Terminal"
bun add next@canary
```
If you are using a stable release, upgrade Next.js with one of the following:
```bash filename="Terminal"
npm i next@latest
```
```bash filename="Terminal"
yarn add next@latest
```
```bash filename="Terminal"
pnpm add next@latest
```
```bash filename="Terminal"
bun add next@latest
```
If you are coming from an older major version, check out our [upgrade guides](/docs/pages/building-your-application/upgrading).
### Note
If you want to report a bug on GitHub, you should upgrade to the newest canary release of Next.js first, to see if the bug has already been fixed in canary.
## Useful Links
- [Upgrade guide](/docs/pages/building-your-application/upgrading)
- [Video: How to Contribute to Open Source (Next.js)](https://www.youtube.com/watch?v=cuoNzXFLitc)
- [Contributing to Next.js](https://github.com/vercel/next.js/blob/canary/contributing.md)
- [Triaging issues](https://github.com/vercel/next.js/blob/canary/contributing/repository/triaging.md)
- [Verifying canary](https://github.com/vercel/next.js/blob/canary/.github/actions/issue-validator/clarify/canary.md)
- [Adding a reproduction](https://github.com/vercel/next.js/blob/canary/.github/actions/issue-validator/clarify/repro.md)
- [Simplifying a reproduction](https://github.com/vercel/next.js/blob/canary/.github/actions/issue-validator/clarify/simplify-repro.md)