vercel__next.js/.github/comments/resolved.md at codex/fallback-root-cache

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

Files

T

Marcos Hernanz 7a5d2f9f32 Allow issue participants to request reopening (#96947 )

## Summary

- Let issue authors and people who commented before closure reopen an
issue within 14 days using `Reopen: <reason>`.
- Limit the automation to unlocked issues closed by triage-or-higher
human maintainers, with ordered timeline checks, bot filtering,
idempotency, and state revalidation.
- Align resolved-issue and contributor guidance with the new reopening
window.

## Verification

- `Prettier 3.6.2 --check .github/workflows/issue_reopen.yml
.github/comments/resolved.md contributing/repository/triaging.md`
- Mocked workflow harness covering 19 closure, eligibility, boundary,
bot, idempotency, and race scenarios
- `autoreview --mode local --stream-engine-output` (Codex and Claude
clean)
- Live GitHub API spot-check for ordered same-second `commented` and
`closed` timeline events
- Not run: live issue close/reopen smoke test (issue-triggered workflows
run only from the default branch)

2026-08-12 15:34:54 -07:00

606 B

Raw Permalink Blame History

This issue has been resolved on a newer version of the package. Please update to next@latest or next@canary to test it out!

If this issue is closed and you think that was a mistake, you can request that it be reopened within the next 14 days. Reply with Reopen: <reason> and explain why the issue is still relevant. If you opened this issue or commented before it was closed, the issue will be reopened automatically.

After 14 days, please open a new issue with the latest version of the package and an up-to-date reproduction, when applicable.

Thank you!

606 B Raw Permalink Blame History

606 B

Raw Permalink Blame History