Deploy v10.21.0

.all-contributorsrc

@@ -13970,6 +13970,15 @@
       "contributions": [
         "content"
       ]
+    },
+    {
+      "login": "koyahness",
+      "name": "Koyah",
+      "avatar_url": "https://avatars.githubusercontent.com/u/210164754?v=4",
+      "profile": "https://github.com/koyahness",
+      "contributions": [
+        "content"
+      ]
     }
   ],
   "contributorsPerLine": 7,

.claude/commands/prepare-release.md

@@ -0,0 +1,163 @@
+---
+description: Prepare a release - version bump, branch sync, release notes cleanup, and deploy PR
+allowed-tools: Bash, Read, Write, AskUserQuestion
+argument-hints: --dry-run|--major|--minor|--patch
+---
+
+# Prepare Release Command
+
+Automates the ethereum.org deployment workflow using `src/scripts/prepare-release.sh` for deterministic operations and Claude for intelligent tasks (version suggestion, release note cleanup).
+
+## Arguments
+
+Details for $ARGUMENTS
+
+- `--dry-run` - Show what would happen without making any changes to remote
+- `--major` - Major release (breaking/stack changes)
+- `--minor` - Minor release (new features, content, translations)
+- `--patch` - Patch release (bug fixes, typos, small updates)
+- _(no flag)_ - Analyze changes and suggest version type
+
+**Dry-run mode**: If `--dry-run` is in `$ARGUMENTS`, pass it as the first argument to ALL script commands. This shows what would happen without pushing to remote or creating PRs.
+
+## Execution Flow
+
+### Step 1: Pre-flight Checks
+
+First, check if `--dry-run` is in `$ARGUMENTS`. If so, set `DRY_RUN_FLAG="--dry-run"`, otherwise set it to empty string.
+
+Run the script to verify environment and sync branches:
+
+```bash
+./src/scripts/prepare-release.sh $DRY_RUN_FLAG preflight
+```
+
+This handles: `gh` authenticated, create worktree if not on `dev`, clean working tree, back-merge `master` → `staging` → `dev`, pull latest.
+
+**Note**: The script can run from any branch. If not on `dev`, it creates a worktree at `/tmp/claude/worktrees/ethereum-org-dev` and performs all operations there.
+
+If this fails, stop and report the error.
+
+### Step 2: Determine Version Type
+
+**If flag provided** (`--major`, `--minor`, `--patch`):
+Extract from `$ARGUMENTS` and proceed to Step 3.
+
+**If no flag provided**:
+1. Fetch draft release: `./src/scripts/prepare-release.sh fetch-draft`
+2. Analyze the changes:
+   - **Major**: Stack/framework changes, significant breaking updates (rare)
+   - **Minor**: New features, new content pages, significant translations, new components
+   - **Patch**: Bug fixes, typo corrections, small content updates, dependency bumps
+3. Provide a ONE-LINE suggestion with reasoning
+4. Use `AskUserQuestion` to confirm: "Proceed with **X** release?" with options: Yes / Change to major / Change to minor / Change to patch
+5. Proceed only after confirmation
+
+### Step 3: Version Bump
+
+```bash
+VERSION=$(./src/scripts/prepare-release.sh $DRY_RUN_FLAG version <type>)
+```
+
+### Step 4: Merge to Staging
+
+```bash
+./src/scripts/prepare-release.sh $DRY_RUN_FLAG merge-staging
+```
+
+### Step 5: Fetch Draft Release
+
+```bash
+DRAFT_JSON=$(./src/scripts/prepare-release.sh fetch-draft)
+```
+
+Parse the JSON to extract `tagName` (DRAFT_TAG) and `body`. If no draft exists, error out.
+
+### Step 6: Clean Release Notes
+
+The draft release body needs cleanup. Apply these filters:
+
+**Remove from CHANGES sections** (lines matching these patterns):
+- Author is `allcontributors` or `allcontributors[bot]` (these are just additions to our all-contributors list, not pertinent to actual changes)
+- PR title contains "Release candidate v" (release management)
+- PR title contains "Deploy v" (release management)
+- PR title starts with "Staging -> dev" or "Staging -> Dev" (back-merge)
+- PR title starts with "Master -> staging" or "Master -> Staging" (back-merge)
+- PR title starts with "Back merge" (back-merge)
+- PR title is just a version number like "v10.20.0" or "v11.0.0" (version bump commits)
+- PR title starts with "Update translation contributors from Crowdin" (automated Crowdin)
+- PR title starts with "Update translation progress from Crowdin" (automated Crowdin)
+
+Note: Keep entries from other bots like `dependabot`, `claude[bot]`, `github-actions` - their PRs ARE meaningful changes (dependency updates, code changes, etc). We just don't thank them as human contributors.
+
+**Remove from CONTRIBUTORS section** (the "Thank you @..." line):
+These accounts should be filtered from the contributors list:
+- `dependabot`
+- `dependabot[bot]`
+- `allcontributors`
+- `allcontributors[bot]`
+- `claude`
+- `claude[bot]`
+- `github-actions`
+- `github-actions[bot]`
+- `actions-user`
+
+**Keep the structure intact**:
+- Keep section headers (⚡️ Changes, 🌐 Translations, 🐛 Bug Fix, etc.)
+- Keep the `***` separators
+- Keep the 🦄 Contributors section (just filter the bot names from it)
+- Remove empty sections if all entries were filtered out
+
+Write cleaned body to temp file:
+```bash
+# Write the cleaned release notes to a temp file
+cat << 'EOF' > /tmp/claude/release-notes.md
+<cleaned_body>
+EOF
+```
+
+### Step 7: Publish Release
+
+```bash
+RELEASE_URL=$(./src/scripts/prepare-release.sh $DRY_RUN_FLAG publish "$VERSION" "$DRAFT_TAG" /tmp/claude/release-notes.md)
+```
+
+### Step 8: Create Deploy PR
+
+```bash
+PR_URL=$(./src/scripts/prepare-release.sh $DRY_RUN_FLAG create-pr "$VERSION" /tmp/claude/release-notes.md)
+```
+
+### Step 9: Cleanup Worktree
+
+If a worktree was created, clean it up:
+
+```bash
+./src/scripts/prepare-release.sh cleanup
+```
+
+### Step 10: Report Success
+
+Output summary:
+```
+✅ Release prepared successfully!
+
+Version: vX.X.X
+Release: <release_url>
+Deploy PR: <pr_url>
+
+Next step: Review the preview build, then merge the PR when ready.
+```
+
+## Error Handling
+
+- If any git operation fails, stop and report the error
+- If `gh` commands fail, check authentication and permissions
+- If no draft release exists, error with clear message
+- If merge conflicts occur during back-merge, stop and instruct user to resolve manually
+
+## Notes
+
+- This command does NOT merge the deploy PR - that remains a manual step after QA
+- The release can be edited after publishing if corrections are needed
+- Always verify the cleaned release notes look correct before the PR is merged

.claude/skills/data-layer/SKILL.md

@@ -0,0 +1,80 @@
+---
+name: data-layer
+description: This skill provides patterns for working with the data-layer module. Use when creating/editing files in src/data-layer/, src/lib/data/, or adding new data sources.
+---
+
+# Data Layer
+
+## Architecture
+
+```
+src/data-layer/           # Isolated, framework-agnostic module
+├── api/                  # Fetch functions (one per data source)
+├── index.ts              # Getter functions (pure passthrough)
+└── registry.ts           # Task registry (hourly/daily)
+
+src/lib/data/             # Next.js caching adapter
+└── index.ts              # Cached wrappers via createCachedGetter()
+```
+
+## Rules
+
+### 1. Getters must be pure passthrough
+
+In `src/data-layer/index.ts`, getter functions must only call `getData<T>(TASK_ID)` with no transformations:
+
+```typescript
+// Correct
+export async function getEventsData(): Promise<EventItem[] | null> {
+  return getData<EventItem[]>(FETCH_EVENTS_TASK_ID)
+}
+
+// Wrong - no transformations in getters
+export async function getEventsData(): Promise<EventItem[] | null> {
+  const data = await getData<EventItem[]>(FETCH_EVENTS_TASK_ID)
+  return data?.map((e) => ({ ...e, computed: derive(e) })) ?? null
+}
+```
+
+All transformations belong in the fetch task (`src/data-layer/api/`), not in the getter.
+
+### 2. Expose via lib/data for caching
+
+When a data function needs caching/revalidation, add a cached wrapper in `src/lib/data/index.ts`:
+
+```typescript
+export const getEventsData = createCachedGetter(
+  dataLayer.getEventsData,
+  ["events-data"],
+  CACHE_REVALIDATE_DAY  // or CACHE_REVALIDATE_HOUR
+)
+```
+
+## Adding a New Data Source
+
+1. Create fetch function in `src/data-layer/api/fetchNewData.ts`:
+   ```typescript
+   export const FETCH_NEW_DATA_TASK_ID = "fetch-new-data"
+
+   export async function fetchNewData(): Promise<YourDataType> {
+     // Fetch and transform data here
+   }
+   ```
+
+2. Add getter in `src/data-layer/index.ts`:
+   ```typescript
+   export async function getNewData(): Promise<YourDataType | null> {
+     return getData<YourDataType>(FETCH_NEW_DATA_TASK_ID)
+   }
+   ```
+
+3. Register in `src/data-layer/registry.ts` (hourlyTasks or dailyTasks)
+
+4. Add cached wrapper in `src/lib/data/index.ts`:
+   ```typescript
+   export const getNewData = createCachedGetter(
+     dataLayer.getNewData,
+     ["new-data"],
+     CACHE_REVALIDATE_HOUR
+   )
+   ```

.env.example

@@ -52,5 +52,8 @@ USE_MOCK_DATA=true
 
 # AWS SES Configuration for Enterprise Contact Form
 # SES_ACCESS_KEY_ID=your_iam_access_key_id
-# SES_SECRET_ACCESS_KEY=your_iam_secret_access_key  
+# SES_SECRET_ACCESS_KEY=your_iam_secret_access_key
 # SES_REGION=us-east-2
+
+# Supabase Events API (Geode Labs)
+# SUPABASE_EVENTS_KEY=your-supabase-publishable-key

.github/labeler.yml

@@ -32,6 +32,3 @@
 "content 🖋️":
   - src/intl/en/**
   - public/content/**/*
-
-"event 📅":
-  - src/data/community-events.json

.github/workflows/claude.yml

@@ -47,7 +47,7 @@ jobs:
           token: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Run Claude PR Action
-        uses: anthropics/claude-code-action@beta
+        uses: anthropics/claude-code-action@v1
         with:
           anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
           timeout_minutes: "60"

.github/workflows/cleanup-netlify-previews.yml

@@ -0,0 +1,104 @@
+name: Cleanup Netlify Preview Deploys
+on:
+  schedule:
+    - cron: '0 0 * * *'
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pull-requests: read
+
+jobs:
+  cleanup:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+        with:
+          fetch-depth: 0
+
+      - name: Cleanup stale preview deploys
+        env:
+          NETLIFY_TOKEN: ${{ secrets.NETLIFY_TOKEN }}
+          NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          # Set to "false" to actually delete, "true" for dry-run
+          DRY_RUN: "false"
+        run: |
+          set -euo pipefail
+
+          echo "=== Netlify Preview Cleanup ==="
+          echo "DRY_RUN: $DRY_RUN"
+          echo ""
+
+          # 1. Fetch deploys with safety pagination
+          ALL_DEPLOYS="[]"
+          for PAGE in {1..100}; do
+            RESPONSE=$(curl -s -H "Authorization: Bearer $NETLIFY_TOKEN" \
+              "https://api.netlify.com/api/v1/sites/$NETLIFY_SITE_ID/deploys?per_page=100&page=$PAGE")
+
+            [[ $(echo "$RESPONSE" | jq 'length') -eq 0 ]] && break
+            ALL_DEPLOYS=$(echo "$ALL_DEPLOYS $RESPONSE" | jq -s 'add')
+          done
+
+          TOTAL_DEPLOYS=$(echo "$ALL_DEPLOYS" | jq 'length')
+          echo "Found $TOTAL_DEPLOYS total deploys"
+
+          # 2. Extract context and state data
+          PREVIEW_DEPLOYS=$(echo "$ALL_DEPLOYS" | jq '[.[] | select(.context == "deploy-preview" or .context == "branch-deploy")]')
+          PREVIEW_COUNT=$(echo "$PREVIEW_DEPLOYS" | jq 'length')
+          echo "Found $PREVIEW_COUNT preview/branch deploys"
+
+          OPEN_PRS=$(gh pr list --state open --json number --jq '.[].number')
+          REMOTE_BRANCHES=$(git branch -r | sed 's/origin\///' | tr -d ' ')
+
+          echo ""
+          echo "=== Processing deploys ==="
+
+          # 3. Process Deploys
+          echo "$PREVIEW_DEPLOYS" | jq -c '.[]' | while read -r DEPLOY; do
+            DEPLOY_ID=$(echo "$DEPLOY" | jq -r '.id')
+            BRANCH=$(echo "$DEPLOY" | jq -r '.branch')
+            CONTEXT=$(echo "$DEPLOY" | jq -r '.context')
+            CREATED=$(echo "$DEPLOY" | jq -r '.created_at')
+            URL=$(echo "$DEPLOY" | jq -r '.deploy_ssl_url // .deploy_url // "no-url"')
+
+            # Never touch production/staging branches
+            if [[ "$BRANCH" == "main" ]] || [[ "$BRANCH" == "master" ]] || [[ "$BRANCH" == "production" ]] || [[ "$BRANCH" == "staging" ]] || [[ "$BRANCH" == "dev" ]]; then
+              continue
+            fi
+
+            SHOULD_DELETE=false
+            REASON=""
+
+            if [[ "$CONTEXT" == "deploy-preview" ]]; then
+              PR_NUM=$(echo "$DEPLOY" | jq -r '.review_url // ""' | grep -oP 'pull/\K[0-9]+' || echo "")
+              if [[ -n "$PR_NUM" ]] && ! echo "$OPEN_PRS" | grep -Fxq "$PR_NUM"; then
+                SHOULD_DELETE=true
+                REASON="PR #$PR_NUM is closed/merged"
+              fi
+            else
+              if ! echo "$REMOTE_BRANCHES" | grep -Fxq "$BRANCH"; then
+                SHOULD_DELETE=true
+                REASON="Branch '$BRANCH' no longer exists"
+              fi
+            fi
+
+            if [ "$SHOULD_DELETE" = true ]; then
+              if [ "$DRY_RUN" = "true" ]; then
+                echo "[DRY-RUN] Would delete: $DEPLOY_ID"
+                echo "          Branch: $BRANCH"
+                echo "          Reason: $REASON"
+                echo "          Created: $CREATED"
+                echo "          URL: $URL"
+                echo ""
+              else
+                echo "Deleting: $DEPLOY_ID ($BRANCH) - $REASON"
+                curl -s -X DELETE -H "Authorization: Bearer $NETLIFY_TOKEN" \
+                  "https://api.netlify.com/api/v1/deploys/$DEPLOY_ID"
+                sleep 1
+              fi
+            fi
+          done
+
+          echo "=== Complete ==="