fix(release): use Node 22 so npm@latest (v12) install succeeds

.github/workflows/release.yml

@@ -32,8 +32,11 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          # Pinned to 20 to match ci.yml.
-          node-version: '20'
+          # Node 22 (Maintenance LTS as of 2026). Node 20 is deprecated on
+          # GitHub runners, so we run on a current supported LTS and use its
+          # bundled npm (already supports --provenance / OIDC publishing).
+          # 22 over 24 (Active LTS) as a conservative, supported floor.
+          node-version: '22'
           check-latest: true
           cache: 'pnpm'
           registry-url: 'https://registry.npmjs.org'
@@ -44,12 +47,6 @@ jobs:
           npm -v
           pnpm -v
 
-      - name: Upgrade npm
-        run: npm install -g npm@latest
-
-      - name: Show npm version after upgrade
-        run: npm -v
-
       - name: Install dependencies
         run: pnpm install --frozen-lockfile
 

src/components/Messaging/MessageList.tsx

@@ -220,7 +220,7 @@ function DateSeparator({ label, className }: DateSeparatorProps) {
       <span
         className={cn(
           'rounded-full px-3 py-1 text-xs font-medium',
-          'bg-neutral-100 text-neutral-500',
+          'bg-neutral-100 text-neutral-600',
           'dark:bg-neutral-800 dark:text-neutral-400'
         )}
       >