Verify canary release

• I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

Deploy template to Vercel Pro team - npx create-turbo@canary -e basic

Which canary version will you have in your reproduction?

turbo 2.4.5-canary.2

Environment information

turbo 2.4.5-canary.2

CLI:
   Version: 2.4.5-canary.2
   Path to executable: /home/tom/Documents/Turborepo-bugged/turbo-priv/node_modules/.pnpm/turbo-linux-64@2.4.5-canary.2/node_modules/turbo-linux-64/bin/turbo
   Daemon status: Not running
   Package manager: pnpm9

Platform:
   Architecture: x86_64
   Operating system: linux
   WSL: false
   Available memory (MB): 9183
   Available CPU cores: 20

Environment:
   CI: None
   Terminal (TERM): xterm-256color
   Terminal program (TERM_PROGRAM): vscode
   Terminal program version (TERM_PROGRAM_VERSION): 1.97.2
   Shell (SHELL): /bin/bash
   stdin: false

Expected behavior

Cache hits should occur on Vercel when making a change to apps/doc (when apps/web is deployed), as experienced when deployed to my personal hobby team (which isn't pro - not sure if this is the cause)?

Actual behavior

Using the basic example template, modifying apps/doc (after deploying apps/web) causes a cache miss every time on Vercel when deployed in a pro team.

Setup: https://www.loom.com/share/5c2f3e8d82e04c5b86ec49aa817cb7f2

Further diagnosis

My hobby team is hitting cache as expected, however the pro team is not.

I deployed again but from my private github account repo to my Vercel hobby team, and to my pro team at the same time. Hobby hits cache as expected, pro team does not. You can see this in this short loom: https://www.loom.com/share/351552a84d364276a3d27555979fc396

To Reproduce

Run npx create-turbo@canary -e basic and deploy one of the apps/* to Vercel pro team. Cache will never hit. Try again with a hobby team and it should hit as expected.

Video showing me setting it up: https://www.loom.com/share/5c2f3e8d82e04c5b86ec49aa817cb7f2

Additional context

This may not be caused by Vercel pro teams in general, perhaps it is some issue with my team in particular - but hopefully this can point you in the right direction 👍