[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Why one Vercel project in a Turborepo monorepo stops triggering deployments

18 views · 2 likes · 2 posts


Raleighfelton (@raleighfelton) · 2026-03-27 · ♥ 1

## Setup

- Turborepo monorepo at `raleighfelton/usefoundry` on GitHub
- 7 Vercel projects, all pointing to `apps/[name]` as root directory
- All deploying from `main` branch
- GitHub App integration (not webhooks)

## Problem

`usefoundry-standard` stopped receiving pushes from GitHub. Commits are confirmed on `origin/main` via `git log` but Vercel never shows them in the deployments list — not even as **Canceled**. Other projects in the same repo are deploying fine.

## What I've Tried

- Multiple disconnect/reconnect of the GitHub repo in project settings
- Every variation of **Ignored Build Step**:
  - `./` 
  - `apps/standard` 
  - `$VERCEL_GIT_PREVIOUS_SHA` 
  - `turbo-ignore` 
  - `exit 1` 
  - "Only build if there are changes"
- Empty commits and real commits — none appear in Vercel’s deployment list
- Confirmed commits are on GitHub `origin/main` 

## Current State

**Ignored Build Step** is set to:

```bash
git diff HEAD^ HEAD --quiet
```

(only build if there are changes). Repo is connected to `main`. Still no deployments appearing for any recent commits.

## Question

Why would one Vercel project in a monorepo stop receiving GitHub pushes entirely while other projects in the same repo continue deploying normally?


Raleighfelton (@raleighfelton) · 2026-03-27 · ♥ 1

There were 4 deploy-test commits pushed after ours. Here are the last 4 actual pushes on main:                                       

  0dc2adf chore(standard): test real change                                                        

  829c8d8 chore(standard): test build trigger                                                      

  6f39ad3 chore(standard): force deploy                                                            

  c880c0d chore(standard): trigger turbo-ignore test                                                                                                          

  The feature commit is at edbb50a -- 5th from HEAD. The 4 commits above it look like deploy/build 


——

15:25:00.709 Running build in  – iad1
15:25:00.710 Build machine configuration: 2 cores, 8 GB
15:25:00.875 Cloning github.com/raleighfelton/usefoundry (Branch: main, Commit: 68abc98)
15:25:01.550 Cloning completed: 673.000ms
15:25:03.896 Restored build cache from previous deployment (4wAqKJgoDmLqsVuMQ4G4Jr1S3Bv9)
15:25:04.030 Running “exit 1”
15:25:04.247 Running “vercel build”
15:25:04.841 Vercel CLI 50.37.1
15:25:04.912 > Detected Turbo. Adjusting default settings…
15:25:05.040 Running “install” command: `npm install --prefix=../..`…
15:25:08.605
15:25:08.606 up to date, audited 587 packages in 3s
15:25:08.607
15:25:08.608 160 packages are looking for funding
15:25:08.608   run `npm fund` for details
15:25:08.644
15:25:08.645 6 vulnerabilities (2 moderate, 3 high, 1 critical)
15:25:08.646
15:25:08.646 To address issues that do not require attention, run:
15:25:08.646   npm audit fix
15:25:08.647
15:25:08.651 To address all issues (including breaking changes), run:
15:25:08.651   npm audit fix --force
15:25:08.651
15:25:08.652 Run `npm audit` for details.
15:25:08.681 Detected Next.js version: 14.2.35
15:25:08.682 Running “turbo run build”
15:25:08.772
15:25:08.772 Attention:
15:25:08.772 Turborepo now collects completely anonymous telemetry regarding usage.
15:25:08.772 This information is used to shape the Turborepo roadmap and prioritize features.
15:25:08.772 You can learn more, including how to opt-out if you’d not like to participate in this anonymous program, by visiting the following URL:
15:25:08.772 https://turborepo.dev/docs/telemetry
15:25:08.773
15:25:08.822 • Packages in scope: @foundry/standard
15:25:08.823 • Running build in 1 packages
15:25:08.823 • Remote caching enabled
15:25:09.069 @foundry/standard:build: cache hit, replaying logs bd7c829448b7121c
15:25:09.069 @foundry/standard:build:
15:25:09.071 @foundry/standard:build: > @foundry/standard@0.1.0 build
15:25:09.071 @foundry/standard:build: > next build
15:25:09.071 @foundry/standard:build:
15:25:09.071 @foundry/standard:build: Attention: Next.js now collects completely anonymous telemetry regarding usage.
15:25:09.071 @foundry/standard:build: This information is used to shape Next.js’ roadmap and prioritize features.
15:25:09.072 @foundry/standard:build: You can learn more, including how to opt-out if you’d not like to participate in this anonymous program, by visiting the following URL:
15:25:09.072 @foundry/standard:build: https://nextjs.org/telemetry
15:25:09.073 @foundry/standard:build:
15:25:09.073 @foundry/standard:build:   ▲ Next.js 14.2.35
15:25:09.073 @foundry/standard:build:
15:25:09.074 @foundry/standard:build:    Creating an optimized production build …
15:25:09.074 @foundry/standard:build:  ⚠ Found lockfile missing swc dependencies, run next locally to automatically patch
15:25:09.075 @foundry/standard:build:  \[webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo\] Resolving ‘nanoid/package.json’ in /vercel/path0/apps/standard/node_modules/next/dist/build for build dependencies doesn’t lead to expected result ‘/vercel/path0/node_modules/nanoid/package.json’, but to ‘/vercel/path0/apps/standard/node_modules/nanoid/package.json’ instead. Resolving dependencies are ignored for this path.
15:25:09.075 @foundry/standard:build:   at unknown 4 nanoid/package.json
15:25:09.075 @foundry/standard:build:   at file dependencies /vercel/path0/apps/standard/node_modules/next/dist/build/webpack-config.js
15:25:09.075 @foundry/standard:build:   at file /vercel/path0/apps/standard/node_modules/next/dist/build/webpack-config.js
15:25:09.075 @foundry/standard:build:   at file dependencies /vercel/path0/apps/standard/node_modules/next/dist/build/webpack/loaders/next-swc-loader.js
15:25:09.076 @foundry/standard:build:   at file /vercel/path0/apps/standard/node_modules/next/dist/build/webpack/loaders/next-swc-loader.js
15:25:09.076 @foundry/standard:build:   at resolve commonjs /vercel/path0/apps/standard/node_modules/next/dist/build/webpack/loaders/next-swc-loader.js
15:25:09.076 @foundry/standard:build:  ⚠ Found lockfile missing swc dependencies, run next locally to automatically patch
15:25:09.076 @foundry/standard:build:  \[webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo\] Resolving ‘nanoid/package.json’ in /vercel/path0/apps/standard/node_modules/next/dist/build for build dependencies doesn’t lead to expected result ‘/vercel/path0/node_modules/nanoid/package.json’, but to ‘/vercel/path0/apps/standard/node_modules/nanoid/package.json’ instead. Resolving dependencies are ignored for this path.
15:25:09.076 @foundry/standard:build:   at unknown 4 nanoid/package.json
15:25:09.077 @foundry/standard:build:   at file dependencies /vercel/path0/apps/standard/node_modules/next/dist/build/webpack-config.js
15:25:09.077 @foundry/standard:build:   at file /vercel/path0/apps/standard/node_modules/next/dist/build/webpack-config.js
15:25:09.077 @foundry/standard:build:   at file dependencies /vercel/path0/apps/standard/node_modules/next/dist/build/webpack/loaders/next-swc-loader.js
15:25:09.077 @foundry/standard:build:   at file /vercel/path0/apps/standard/node_modules/next/dist/build/webpack/loaders/next-swc-loader.js
15:25:09.077 @foundry/standard:build:   at resolve commonjs /vercel/path0/apps/standard/node_modules/next/dist/build/webpack/loaders/next-swc-loader.js
15:25:09.077 @foundry/standard:build:  \[webpack.cache.PackFileCacheStrategy\] Serializing big strings (140kiB) impacts deserialization performance (consider using Buffer instead and decode when needed)
15:25:09.077 @foundry/standard:build:  ⚠ Found lockfile missing swc dependencies, run next locally to automatically patch
15:25:09.077 @foundry/standard:build:  \[webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo\] Resolving ‘nanoid/package.json’ in /vercel/path0/apps/standard/node_modules/next/dist/build for build dependencies doesn’t lead to expected result ‘/vercel/path0/node_modules/nanoid/package.json’, but to ‘/vercel/path0/apps/standard/node_modules/nanoid/package.json’ instead. Resolving dependencies are ignored for this path.
15:25:09.079 @foundry/standard:build:   at unknown 4 nanoid/package.json
15:25:09.079 @foundry/standard:build:   at file dependencies /vercel/path0/apps/standard/node_modules/next/dist/build/webpack-config.js
15:25:09.079 @foundry/standard:build:   at file /vercel/path0/apps/standard/node_modules/next/dist/build/webpack-config.js
15:25:09.079 @foundry/standard:build:   at file dependencies /vercel/path0/apps/standard/node_modules/next/dist/build/webpack/loaders/next-swc-loader.js
15:25:09.079 @foundry/standard:build:   at file /vercel/path0/apps/standard/node_modules/next/dist/build/webpack/loaders/next-swc-loader.js
15:25:09.080 @foundry/standard:build:   at resolve commonjs /vercel/path0/apps/standard/node_modules/next/dist/build/webpack/loaders/next-swc-loader.js
15:25:09.080 @foundry/standard:build:  ✓ Compiled successfully
15:25:09.080 @foundry/standard:build:    Linting and checking validity of types …
15:25:09.080 @foundry/standard:build:    Collecting page data …
15:25:09.080 @foundry/standard:build:  ⚠ Found lockfile missing swc dependencies, run next locally to automatically patch
15:25:09.080 @foundry/standard:build:    Generating static pages (0/9) …
15:25:09.081 @foundry/standard:build:    Generating static pages (2/9)
15:25:09.081 @foundry/standard:build:    Generating static pages (4/9)
15:25:09.081 @foundry/standard:build:    Generating static pages (6/9)
15:25:09.081 @foundry/standard:build:  ✓ Generating static pages (9/9)
15:25:09.081 @foundry/standard:build:    Finalizing page optimization …
15:25:09.081 @foundry/standard:build:    Collecting build traces …
15:25:09.081 @foundry/standard:build:
15:25:09.081 @foundry/standard:build: Route (app)                              Size     First Load JS
15:25:09.081 @foundry/standard:build: ┌ ƒ /                                    5.87 kB         151 kB
15:25:09.081 @foundry/standard:build: ├ ƒ /\_not-found                          873 B          88.2 kB
15:25:09.082 @foundry/standard:build: ├ ƒ /api/extract                         0 B                0 B
15:25:09.082 @foundry/standard:build: ├ ƒ /api/generate                        0 B                0 B
15:25:09.082 @foundry/standard:build: ├ ƒ /api/publish                         0 B                0 B
15:25:09.082 @foundry/standard:build: ├ ƒ /api/regenerate                      0 B                0 B
15:25:09.082 @foundry/standard:build: ├ ƒ /editor                              12.5 kB         178 kB
15:25:09.082 @foundry/standard:build: └ ƒ /guidelines/\[brandId\]                5.62 kB         169 kB
15:25:09.082 @foundry/standard:build: + First Load JS shared by all            87.3 kB
15:25:09.082 @foundry/standard:build:   ├ chunks/117-634dd91f294f7aa2.js       31.7 kB
15:25:09.082 @foundry/standard:build:   ├ chunks/fd9d1056-cff0b72c37e203ae.js  53.6 kB
15:25:09.082 @foundry/standard:build:   └ other shared chunks (total)          1.95 kB
15:25:09.083 @foundry/standard:build:
15:25:09.083 @foundry/standard:build:
15:25:09.083 @foundry/standard:build: ƒ Middleware                             74.5 kB
15:25:09.083 @foundry/standard:build:
15:25:09.083 @foundry/standard:build: ƒ  (Dynamic)  server-rendered on demand
15:25:09.083 @foundry/standard:build:
15:25:09.083
15:25:09.083   Tasks:    1 successful, 1 total
15:25:09.083  Cached:    1 cached, 1 total
15:25:09.083    Time:    283ms >>> FULL TURBO
15:25:09.084 Summary:    /vercel/path0/.turbo/runs/3BXdmkYYGMXxQtoBIKIe6xordnj.json
15:25:09.084
15:25:09.269 Traced Next.js server files in: 41.501ms
15:25:09.342 Created all serverless functions in: 72.766ms
15:25:09.433 Collected static files (public/, static/, .next/static): 5.476ms
15:25:09.478 Build Completed in /vercel/output \[4s\]
15:25:09.882 Deploying outputs…