chore(web): rename apps/web package to eventrelay-web (F8a) - #1451
Conversation
Replace the leftover next-enterprise-era name building-production-ai-infrastructure-platform with eventrelay-web so the workspace package matches the EventRelay product monorepo.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 1 minute You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository YAML (base), Repository UI (inherited), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
added
the
documentation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsEnsure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice. Scanned FilesNone |
|
@coderabbitai review Triggering explicitly: this PR has had no review. The auto-review was skipped with Timing, for whoever argues #1424 (all on head
The skip status was written 15s after the qualifying label landed, on a PR that was never a draft. That is tighter than the #1440 case, but still not decisive on its own: the post time is not the evaluation time, so CodeRabbit may have evaluated at Independent of the review gate, I ran the red-team pass over the diff. No findings. The rename is complete and internally consistent:
The only remaining mention of the old name anywhere is the deliberate historical one in Still open: Generated by Claude Code |
|
@coderabbitai review Auto-review skipped again with "Auto reviews are limited based on label configuration" — this PR carries Red-team pass — no findingsRan the runbook's step-5 pass over the diff before requesting review. A monorepo package rename's real failure mode is a dangling reference, so that is what I went looking for.
The claims worth attacking, if you want somewhere to start:
CI on
|
|
✏️ Learnings added
|
Green — terminal state
|
| Check | Result |
|---|---|
test |
success (20:17:07) |
Generate and Upload Coverage |
success (20:19:11) — the conditionally-required one, since this diff touches apps/** |
No check is failing. This closes the two unchecked boxes in the description ("Required CI green on current head").
On the review gate — read the green CodeRabbit status carefully
My @coderabbitai review request above did not produce a review. The CodeRabbit commit status on this head now reads Review rate limited — and reports it as success.
That makes four distinct reasons this repo emits a green CodeRabbit status, none of which mean "reviewed":
Review skipped: excluded by label configuration(the malformedauto_review.labelsscalar)auto_review.drafts: falsepath_filtersexclusionReview rate limited← this PR, now
MERGE_POLICY.md gate 3 is satisfied either way — "a reviewer that skips for configuration reasons satisfies this gate", and rate-limiting is a decline to look, not a finding. But I would rather say plainly that this PR has had no automated code review than let a green badge imply otherwise. The only review it has received is my red-team pass in the previous comment, which found nothing.
Given the change — three files, a package-name string, and a regenerated lockfile link entry, with build/test/lint-frontend all passing on it — I do not think that gap is worth blocking on. Recording it rather than papering over it.
Staged merge command
gh pr merge 1451 --squash --repo groupthinking/EventRelay
Not merging automatically: no automerge label, and main is protected. Class A under MERGE_POLICY.md §8 (docs + CI-adjacent config, no runtime surface).
Generated by Claude Code
|
Tip For best results, initiate chat on the files or code changes.
Based on your reported check results, the required CI is green and the PR is mergeable. No CodeRabbit finding blocks the package rename. A maintainer can now make the merge decision. ✏️ Learnings added
You are interacting with an AI system. |
CI is now complete and green — and a caution on the comment aboveUpdating my earlier note:
So the two unchecked boxes in the PR description can be reconciled: required CI is green on this head, and there are zero review threads (
|
🧩 Analysis chain🏁 Script executed: #!/bin/bash
set -euo pipefail
echo '--- HEAD ---'
git rev-parse HEAD
echo '--- DIFF STAT ---'
git diff --stat HEAD^ HEAD
echo '--- DIFF ---'
git diff --no-ext-diff --unified=80 HEAD^ HEAD -- \
apps/web/package.json package-lock.json docs/F8_WEB_OWNERSHIP.md
echo '--- STRUCTURE: package manifests and workspace configuration ---'
fd -HI -t f -g 'package.json' -g 'turbo.json' -g 'vercel.json' -g 'Dockerfile*' -g '*.yml' -g '*.yaml' | sed -n '1,240p'
echo '--- OLD PACKAGE-NAME REFERENCES IN TRACKED FILES ---'
git grep -n -I -- 'building-production-ai-infrastructure-platform' || true
echo '--- NEW PACKAGE-NAME REFERENCES IN TRACKED FILES ---'
git grep -n -I -- 'eventrelay-web' || true
echo '--- PACKAGE MANIFEST NAMES ---'
while IFS= read -r file; do
printf '%s: ' "$file"
jq -r '.name // "<no name>"' "$file"
done < <(fd -HI -t f -g 'package.json' | sort)
echo '--- ROOT PACKAGE AND TURBO CONFIGURATION ---'
cat -n package.json
if [ -f turbo.json ]; then cat -n turbo.json; fi
echo '--- LOCKFILE WORKSPACE ENTRIES ---'
jq -r '
.lockfileVersion as $v
| "lockfileVersion=\($v)",
(.packages["apps/web"] | "apps/web name=\(.name)"),
(.packages["node_modules/eventrelay-web"] | "eventrelay-web link=\(.link) resolved=\(.resolved)"),
(.packages["node_modules/building-production-ai-infrastructure-platform"] // empty | "old link entry still exists")
' package-lock.jsonLength of output: 16493 🏁 Script executed: #!/bin/bash
set -euo pipefail
echo '--- OLD PACKAGE-NAME REFERENCES IN TRACKED FILES ---'
git grep -n -I -- 'building-production-ai-infrastructure-platform' || true
echo '--- NEW PACKAGE-NAME REFERENCES IN TRACKED FILES ---'
git grep -n -I -- 'eventrelay-web' || true
echo '--- PACKAGE/DEPLOYMENT CONFIGURATION FILES ---'
fd -HI -t f . \
-g 'package.json' -g 'turbo.json' -g 'vercel.json' -g 'Dockerfile*' \
-g '*.yml' -g '*.yaml' -g '*.json' \
-E node_modules -E .git | sort | sed -n '1,320p'
echo '--- PACKAGE MANIFEST NAMES ---'
while IFS= read -r file; do
printf '%s: ' "$file"
jq -r '.name // "<no name>"' "$file"
done < <(fd -HI -t f -g 'package.json' -E node_modules -E .git | sort)
echo '--- WORKSPACE, TURBO, VERCEL, AND PACKAGE-NAME COMMANDS ---'
for file in package.json turbo.json vercel.json; do
if [ -f "$file" ]; then
echo "### $file"
cat -n "$file"
fi
done
rg -n -I -C 3 --hidden \
-g '!node_modules/**' -g '!.git/**' \
-e -- '--(?:filter|workspace)(?:=|\s)' \
-e -- '\bnpm\s+(?:run|exec|--workspace)\b' \
-e -- '\b(?:docker|podman)\s+build\b' \
-e -- '\b(?:turbo|vercel)\b' \
.github . 2>/dev/null || true
echo '--- LOCKFILE INTEGRITY ---'
jq -e '
.lockfileVersion == 3
and .packages["apps/web"].name == "eventrelay-web"
and .packages["node_modules/eventrelay-web"].link == true
and .packages["node_modules/eventrelay-web"].resolved == "apps/web"
and (.packages["node_modules/building-production-ai-infrastructure-platform"] | not)
' package-lock.json
jq -r '
[
.packages
| to_entries[]
| select(.value.link == true and .value.resolved == "apps/web")
| .key
] | "apps/web link entries: \(join(", ")) (count=\(length))"
' package-lock.jsonLength of output: 2967 🏁 Script executed: #!/bin/bash
set -euo pipefail
echo '--- LOCKFILE JSON AND WORKSPACE-LINK INTEGRITY ---'
jq -e '
.lockfileVersion == 3
and .packages["apps/web"].name == "eventrelay-web"
and .packages["node_modules/eventrelay-web"].link == true
and .packages["node_modules/eventrelay-web"].resolved == "apps/web"
and (.packages["node_modules/building-production-ai-infrastructure-platform"] | not)
' package-lock.json
jq -r '
[
.packages
| to_entries[]
| select(.value.link == true and .value.resolved == "apps/web")
| .key
] | "apps/web link entries: \(join(", ")) (count=\(length))"
' package-lock.json
echo '--- PACKAGE MANIFEST NAMES ---'
find . -type d \( -name .git -o -name node_modules \) -prune -o \
-type f -name package.json -print | sort |
while IFS= read -r file; do
printf '%s: ' "${file#./}"
jq -r '.name // "<no name>"' "$file"
done
echo '--- ROOT WORKSPACE AND TURBO CONFIGURATION ---'
for file in package.json turbo.json vercel.json; do
if [ -f "$file" ]; then
echo "### $file"
cat -n "$file"
fi
done
echo '--- WORKFLOW AND DEPLOYMENT FILES ---'
find . -type d \( -name .git -o -name node_modules \) -prune -o \
-type f \( -name '*.yml' -o -name '*.yaml' -o -name 'Dockerfile*' \) -print |
sort | sed -n '1,240p'
echo '--- PACKAGE-NAME SELECTORS AND BUILD CONTEXTS ---'
rg -n -I -C 3 --hidden \
-g '!node_modules/**' -g '!.git/**' \
-e -- '--(?:filter|workspace)(?:=|\s)' \
-e -- '\b(?:npm|pnpm|yarn)\s+(?:run|exec|--workspace)\b' \
-e -- '\b(?:docker|podman)\s+build\b' \
-e -- '\b(?:turbo|vercel)\b' \
. || trueLength of output: 2017 🏁 Script executed: #!/bin/bash
set -euo pipefail
echo '--- LOCKFILE JSON AND WORKSPACE-LINK INTEGRITY ---'
git show HEAD:package-lock.json | jq -e '
.lockfileVersion == 3
and .packages["apps/web"].name == "eventrelay-web"
and .packages["node_modules/eventrelay-web"].link == true
and .packages["node_modules/eventrelay-web"].resolved == "apps/web"
and (.packages["node_modules/building-production-ai-infrastructure-platform"] | not)
'
git show HEAD:package-lock.json | jq -r '
[
.packages
| to_entries[]
| select(.value.link == true and .value.resolved == "apps/web")
| .key
] | "apps/web link entries: \(join(", ")) (count=\(length))"
'
echo '--- PACKAGE MANIFEST NAMES ---'
git ls-tree -r --name-only HEAD |
grep -E '(^|/)package\.json$' |
sort |
while IFS= read -r file; do
printf '%s: ' "$file"
git show "HEAD:$file" | jq -r '.name // "<no name>"'
done
echo '--- ROOT WORKSPACE AND TURBO CONFIGURATION ---'
for file in package.json turbo.json vercel.json; do
if git cat-file -e "HEAD:$file" 2>/dev/null; then
echo "### $file"
git show "HEAD:$file" | cat -n
fi
done
echo '--- PACKAGE-NAME SELECTORS AND BUILD CONTEXTS IN TRACKED FILES ---'
git grep -n -I -E \
-- '--(filter|workspace)(=|[[:space:]])|(^|[[:space:]])(npm|pnpm|yarn)[[:space:]]+(run|exec|--workspace)\b|(^|[[:space:]])(docker|podman)[[:space:]]+build\b|\b(turbo|vercel)\b' \
HEAD -- \
':!package-lock.json' ':!docs/F8_WEB_OWNERSHIP.md' || true
echo '--- OLD PACKAGE-NAME REFERENCES IN HEAD ---'
git grep -n -I -- 'building-production-ai-infrastructure-platform' HEAD || trueLength of output: 135867
I verified the package rename at
I did not execute builds or tests in the sandbox. The rename does not introduce an identified runtime, deployment, or workspace-resolution risk.
|
Review gate now satisfied — correcting my previous commentMy last comment said "no automated review has run on this PR." That is no longer true — the retried The two passes were independent and agree point-for-point:
It also covered one thing I did not: that CI and Docker build commands select Worth keeping straight for anyone auditing this thread later: CodeRabbit's conversational reply earlier — "the required CI is green and the PR is mergeable" — was an echo of my input and was wrong when written. This result is the real review: it ran scripts, reported output lengths, and reached its conclusions independently. Two different things from the same bot, minutes apart, and only the second is evidence. One caveat it stated itself: it did not execute builds or tests. CI did — Terminal state unchanged:
|
|
Tip For best results, initiate chat on the files or code changes.
The earlier conversational reply was not independent CI verification. It should not have stated that CI was green or that the PR was mergeable from reported status alone. The current evidence is sufficient for the technical review gate:
✏️ Learnings added
You are interacting with an AI system. |
1 participant
Canonical issue
Closes #1450
Outcome
The Next.js workspace package is named
eventrelay-web, matching the EventRelay monorepo instead of the leftover boilerplate namebuilding-production-ai-infrastructure-platform.Scope
apps/web/package.json, rootpackage-lock.json,docs/F8_WEB_OWNERSHIP.mdRisk
private: true); no publish surfaceVerification
Head
8090463ecc928fdcb60d7d573e0c1192355bb2cc./health→ 200 withauth_mode=open_dev,video_path_ready=true/api/v1/health→ 200 underALLOW_UNAUTHENTICATED=1Production evidence
Local backend smoke on this machine (not a production deploy). Package rename has no production URL impact (
private: true).Agent handoff
Agent provenance
Human-authored (Grok Build on Dev canonical tree).