Balázs Orbán dc109bf6c9 chore: indicate staleness more prominently in next info output (#60376) ... ### What? Improve the `next info` output. <details> <summary>Before: </summary> <img src="https://github.com/vercel/next.js/assets/18369201/735da72f-6746-42a0-838d-e10db78b2db3"> </details> <details> <summary>After: </summary> <img src="https://github.com/vercel/next.js/assets/18369201/d72c0027-71d9-494c-bb98-dd0fed99c8d9"> </details> ### Why? People have been ignoring the ask to check `next@canary` before opening a new issue, which results in triaging overhead. This PR inlines the warning into `next info` that would make it an extra effort to remove the warning without reading the message, hopefully leading to not ignoring the message anymore. ### How? Reusing the same logic from the version staleness indicator from Error Overlay. [Slack thread](https://vercel.slack.com/archives/C03KAR5DCKC/p1704364764719949)		2024-01-19 18:36:19 +01:00
..
1.bug_report.yml	chore: indicate staleness more prominently in next info output (#60376)	2024-01-19 18:36:19 +01:00
2.example_bug_report.yml	chore(docs): update next export to output: 'export' (#47717)	2023-03-31 02:04:23 +00:00
4.docs_request.yml	[Next Docs] Update Git Workflow (#50579)	2023-06-08 12:01:55 +02:00
config.yml	chore: improve repo templates (#46629)	2023-03-01 09:25:51 -08:00