Merge branch 'main' into fix/consistent-color-transitions

.github/workflows/build.yml

@@ -89,7 +89,7 @@ jobs:
             ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}-
 
       - name: Set up Node.js
-        uses: actions/setup-node@0a44ba7841725637a19e28fa30b79a866c81b0a6 # v4.0.4
+        uses: actions/setup-node@39370e3970a6d050c480ffad4ff0ed4d3fdee5af # v4.1.0
         with:
           # We want to ensure that the Node.js version running here respects our supported versions
           node-version-file: '.nvmrc'

.github/workflows/lint-and-tests.yml

@@ -95,7 +95,7 @@ jobs:
             cache-lint-
 
       - name: Set up Node.js
-        uses: actions/setup-node@0a44ba7841725637a19e28fa30b79a866c81b0a6 # v4.0.4
+        uses: actions/setup-node@39370e3970a6d050c480ffad4ff0ed4d3fdee5af # v4.1.0
         with:
           # We want to ensure that the Node.js version running here respects our supported versions
           node-version-file: '.nvmrc'
@@ -173,7 +173,7 @@ jobs:
           fetch-depth: 0
 
       - name: Set up Node.js
-        uses: actions/setup-node@0a44ba7841725637a19e28fa30b79a866c81b0a6 # v4.0.4
+        uses: actions/setup-node@39370e3970a6d050c480ffad4ff0ed4d3fdee5af # v4.1.0
         with:
           # We want to ensure that the Node.js version running here respects our supported versions
           node-version-file: '.nvmrc'

.github/workflows/translations-pr.yml

@@ -97,7 +97,7 @@ jobs:
             cache-lint-
 
       - name: Set up Node.js
-        uses: actions/setup-node@0a44ba7841725637a19e28fa30b79a866c81b0a6 # v4.0.4
+        uses: actions/setup-node@39370e3970a6d050c480ffad4ff0ed4d3fdee5af # v4.1.0
         with:
           # We want to ensure that the Node.js version running here respects our supported versions
           node-version-file: '.nvmrc'

apps/site/package.json

@@ -55,7 +55,7 @@
     "@savvywombat/tailwindcss-grid-areas": "~4.0.0",
     "@sentry/nextjs": "^8.33.1",
     "@tailwindcss/container-queries": "~0.1.1",
-    "@types/node": "20.16.5",
+    "@types/node": "20.17.5",
     "@vcarl/remark-headings": "~0.1.0",
     "@vercel/analytics": "~1.3.1",
     "@vercel/speed-insights": "~1.0.12",
@@ -82,7 +82,7 @@
     "remark-gfm": "~4.0.0",
     "remark-reading-time": "~2.0.1",
     "semver": "~7.6.3",
-    "shiki": "~1.17.5",
+    "shiki": "~1.22.2",
     "tailwindcss": "^3.4.13",
     "unist-util-visit": "~5.0.0",
     "vfile": "~6.0.3",
@@ -96,11 +96,11 @@
     "@storybook/addon-themes": "~8.3.5",
     "@storybook/addon-viewport": "~8.3.5",
     "@storybook/nextjs": "~8.3.5",
-    "@testing-library/jest-dom": "~6.5.0",
+    "@testing-library/jest-dom": "~6.6.3",
     "@testing-library/react": "~16.0.1",
     "@testing-library/user-event": "~14.5.2",
-    "@types/jest": "29.5.13",
-    "@types/react": "^18.3.11",
+    "@types/jest": "29.5.14",
+    "@types/react": "^18.3.12",
     "@types/react-dom": "^18.3.0",
     "@types/semver": "~7.5.8",
     "eslint-config-next": "15.0.0-rc.1",
@@ -120,7 +120,7 @@
     "stylelint-config-standard": "36.0.1",
     "stylelint-order": "6.0.4",
     "stylelint-selector-bem-pattern": "4.0.1",
-    "typescript": "~5.5.4",
+    "typescript": "~5.6.3",
     "typescript-eslint": "~8.8.1",
     "user-agent-data-types": "0.4.2"
   }

apps/site/pages/en/learn/getting-started/profiling.md

@@ -5,6 +5,12 @@ layout: learn
 
 # Profiling Node.js Applications
 
+Profiling a Node.js application involves measuring its performance by analyzing
+the CPU, memory, and other runtime metrics while the application is running.
+This helps in identifying bottlenecks, high CPU usage, memory leaks, or slow
+function calls that may impact the application's efficiency, responsiveness
+and scalability.
+
 There are many third party tools available for profiling Node.js applications
 but, in many cases, the easiest option is to use the Node.js built-in profiler.
 The built-in profiler uses the [profiler inside V8][] which samples the stack at