Skip to content

chore: force Vercel cache rebuild #256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
leoisadev1 merged 1 commit into from
Nov 8, 2025
Merged

chore: force Vercel cache rebuild #256

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions apps/web/.vercel-cache-bust
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# Vercel Cache Bust

This file forces Vercel to rebuild with a fresh cache.

Build timestamp: 2025-11-08T02:10:00Z
Reason: Fix build cache corruption issue
Comment on lines +1 to +6

@greptile-apps greptile-apps Bot Nov 8, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

logic: Simply adding a new file may not invalidate Vercel's .next build cache. Vercel caches the .next/ directory between builds, and adding unrelated files typically doesn't trigger cache invalidation.

Consider these more reliable approaches:

  1. Add VERCEL_FORCE_NO_BUILD_CACHE=1 environment variable in Vercel dashboard (temporary)
  2. Modify next.config.js with a build ID or cache invalidation
  3. Use Vercel CLI: vercel build --force
  4. Clear cache via Vercel dashboard: Settings → Caching → Clear Build Cache

Score: 4/5 - High confidence this won't work as intended. The build will run, but likely reuse the corrupted .next cache.

Loading