chore: update labels in workflows/templates (#63713)

.github/ISSUE_TEMPLATE/1.bug_report.yml

@@ -1,6 +1,6 @@
 name: Bug Report
 description: Create a bug report for the Next.js core
-labels: ['template: bug']
+labels: ['bug']
 body:
   - type: markdown
     attributes:
@@ -71,29 +71,30 @@ body:
       multiple: true
       options:
         - 'Not sure'
-        - 'App Router'
-        - 'CLI (create-next-app)'
-        - 'Data fetching (gS(S)P, getInitialProps)'
-        - 'Dynamic imports (next/dynamic)'
-        - 'ESLint (eslint-config-next)'
-        - 'Font optimization (next/font)'
-        - 'Image optimization (next/image, next/legacy/image)'
+        - 'create-next-app'
+        - 'Documentation'
+        - 'Lazy Loading'
+        - 'Font (next/font)'
+        - 'Image (next/image)'
+        - 'Instrumentation'
         - 'Internationalization (i18n)'
-        - 'Jest (next/jest)'
-        - 'MDX (@next/mdx)'
-        - 'Metadata (metadata, generateMetadata, next/head)'
-        - 'Middleware / Edge (API routes, runtime)'
-        - 'Module resolution (CJS / ESM, module resolving)'
-        - 'Operating System (Windows, MacOS, Linux)'
-        - 'Package manager (npm, pnpm, Yarn)'
-        - 'Routing (next/router, next/navigation, next/link)'
-        - 'Script optimization (next/script)'
-        - 'Standalone mode (output: "standalone")'
-        - 'Static HTML Export (output: "export")'
-        - 'SWC minifier (swcMinify: true)'
-        - 'SWC transpilation'
-        - 'Turbopack (--turbo)'
-        - 'TypeScript (plugin, built-in types)'
+        - 'Linting'
+        - 'Markdown (MDX)'
+        - 'Metadata'
+        - 'Middleware'
+        - 'Output (export/standalone)'
+        - 'Pages Router'
+        - 'Parallel & Intercepting Routes'
+        - 'Partial Prerendering (PPR)'
+        - 'Performance'
+        - 'Runtime'
+        - 'Script (next/script)'
+        - 'Testing'
+        - 'Turbopack'
+        - 'TypeScript'
+        - 'SWC'
+        - 'Upstream'
+
     validations:
       required: true
   - type: dropdown

.github/ISSUE_TEMPLATE/2.example_bug_report.yml

@@ -1,6 +1,6 @@
 name: Bug Report for Examples
 description: Create a bug report for one of the Next.js examples
-labels: ['area: examples']
+labels: ['example bug']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/4.docs_request.yml

@@ -2,7 +2,7 @@ name: 'Docs Request for an Update or Improvement'
 description: A request to update or improve Next.js documentation
 title: 'Docs: '
 labels:
-  - 'template: documentation'
+  - 'documentation'
 body:
   - type: markdown
     attributes:

.github/labeler.json

@@ -1,11 +1,11 @@
 {
   "labels": {
-    "area: create-next-app": ["packages/create-next-app/**"],
-    "area: documentation": ["docs/**", "errors/**"],
-    "area: examples": ["examples/**"],
-    "area: Font Optimization": ["**/*font*"],
-    "area: tests": ["test/**", "bench/**"],
-    "area: Turbopack": ["packages/next-swc/crates/next-*/**"],
+    "create-next-app": ["packages/create-next-app/**"],
+    "documentation": ["docs/**", "errors/**"],
+    "examples": ["examples/**"],
+    "Font (next/font)": ["**/*font*"],
+    "tests": ["test/**", "bench/**"],
+    "Turbopack": ["packages/next-swc/crates/next-*/**"],
     "created-by: Chrome Aurora": [
       { "type": "user", "pattern": "atcastle" },
       { "type": "user", "pattern": "devknoll" },
@@ -46,7 +46,7 @@
       { "type": "user", "pattern": "timeyoutakeit" },
       { "type": "user", "pattern": "manovotny" }
     ],
-    "created-by: turbopack team": [
+    "created-by: Turbopack team": [
       { "type": "user", "pattern": "bgw" },
       { "type": "user", "pattern": "ForsakenHarmony" },
       { "type": "user", "pattern": "kdy1" },
@@ -65,7 +65,6 @@
       "packages/next-mdx/**",
       "packages/next-swc/**",
       "packages/next/**",
-      "packages/react-dev-overlay/**",
       "packages/react-refresh-utils/**"
     ]
   }

.github/workflows/triage.yml

@@ -19,7 +19,7 @@ jobs:
     steps:
       - uses: balazsorban44/[email protected]
         with:
-          label-area-prefix: 'area:'
+          label-area-prefix: 'bug'
           label-area-section: 'Which area\(s\) are affected\? \(Select all that apply\)(.*)### Additional context'
           label-comments: |
             {
@@ -34,5 +34,5 @@ jobs:
           reproduction-blocklist: 'github.com/vercel/next.js.*,github.com/\\w*/?$,github.com$'
           reproduction-link-section: '### Link to the code that reproduces this issue(.*)### To Reproduce'
           reproduction-invalid-label: 'invalid link'
-          reproduction-issue-labels: 'template: bug,'
+          reproduction-issue-labels: 'bug,'
           comment-unhelpful-weight: 0.5

contributing/repository/triaging.md

@@ -6,17 +6,17 @@ Repository maintainers triage every issue and PR opened in the repository.
 
 Issues are opened with one of these labels:
 
-- `template: bug` - unverified issue with Next.js itself
-- `template: documentation` - feedback for improvement or an unverified issue with the Next.js documentation
-- `area: examples` - an issue with one of the examples in the [`examples`](https://github.com/vercel/next.js/tree/canary/examples) folder
+- `bug` - issue with Next.js itself
+- `documentation` - feedback for improvement or an issue with the Next.js documentation
+- `example bug` - an issue with one of the examples in the [`examples`](https://github.com/vercel/next.js/tree/canary/examples) folder
 
 ## Bug reports
 
 ### Automated triaging
 
 In case of a bug report, **if the reproduction is missing or insufficient, the issue is automatically closed**, and a comment is added with a correct course of action. The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/invalid-link.md). We also add an `invalid link` label to mark the issue. To avoid your issue being closed, please follow the [bug report template](https://github.com/vercel/next.js/blob/canary/.github/ISSUE_TEMPLATE/1.bug_report.yml) carefully.
 
-If you filled out the "Which area(s) are affected? (Select all that apply)" section of the bug report template, we will add the corresponding `area:` label(s).
+If you fill out the "Which area(s) are affected? (Select all that apply)" section of the bug report template, we will add the corresponding [label(s)](https://github.com/vercel/next.js/labels).
 
 ### Manual triaging
 
@@ -26,7 +26,7 @@ A maintainer can also manually label an issue with one of the following labels,
 
 1. `please add a complete reproduction`
 
-The provided reproduction is not enough for the maintainers to investigate. If a sufficient reproduction is not provided for more than 30 days, the issue becomes stale and will be automatically closed. If a reproduction is provided within 30 days, a `needs triage` label is added, indicating that the issue needs another look from a maintainer.
+The provided reproduction is not enough for the maintainers to investigate. If sufficient reproduction is not provided for more than 30 days, the issue becomes stale and will be automatically closed. If a reproduction is provided within 30 days, a `needs triage` label is added, indicating that the issue needs another look from a maintainer.
 
 The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/comments/invalid-reproduction.md)
 
@@ -53,7 +53,7 @@ The issue will receive [this comment](https://github.com/vercel/next.js/blob/can
 
 ## Verified issues
 
-If an issue is verified, it will receive the `linear: next`, `linear: dx` or `linear: web` label and will be tracked by the maintainers. Additionally, one or more `area:` label(s) can be added to indicate which part of Next.js is affected.
+If an issue is verified, it will receive the `linear: next`, `linear: dx` or `linear: web` label and will be tracked by the maintainers. Additionally, one or more [label(s)](https://github.com/vercel/next.js/labels) can be added to indicate which part of Next.js is affected.
 
 Confirmed issues never become stale or are closed before resolution.
 

release.js

@@ -1,8 +1,8 @@
 // section -> label
 const sectionLabelMap = {
   'Core Changes': 'type: next',
-  'Documentation Changes': 'area: documentation',
-  'Example Changes': 'area: examples',
+  'Documentation Changes': 'documentation',
+  'Example Changes': 'examples',
 }
 
 const fallbackSection = 'Misc Changes'