this one is about the git author on the commit, not just your account. on hobby with a private repo vercel only deploys commits authored by the hobby team owner, and it checks that by matching the author email to the github login connected to your vercel account. so look at the top commit with git log and read the exact author email, then open that commit on github and see if it is linked to your user. if it is not, set git config user.email to an email verified on your github account (if you use github private email, use the full noreply address from your github email settings), make a new empty commit and deploy again. no history rewrite needed. if it still fails, post what git log shows with the email blurred and we can narrow it down

Thanks for your help. I have an important update.

The TEAM_ACCESS_REQUIRED error no longer occurred after creating a new empty commit and using a valid CLI token.

However, the deployment still fails during npm run build because my release integrity check detects a SHA-256 mismatch in vercel.json.

I investigated the exact deployment using Vercel's Deployment Files API.

Verified findings:

• Local vercel.json: 50 bytes, SHA-256 d8209115a448d5e218f94369a0a9703c7213cf26d71c967565b341d104100ea7
• GitHub vercel.json: identical
• File retrieved from the failed deployment using Vercel's API: identical, 50 bytes
• File read in the Vercel build environment: 64 bytes, SHA-256 4cc26eab9f2cbee1bf6719e932b25c69aed623d2e80d5d40045884bd8529d586

The 64-byte version was already present when my postprepare diagnostic ran, and remained unchanged through prebuild and the verification step.

Deployment ID: dpl_7ykFTrj7724cKZtpaVBDEhZ1B77g

Does Vercel intentionally transform or regenerate vercel.json while preparing the build environment?

Is there a recommended way to preserve the original file bytes or identify the process responsible for this difference?

I would like to keep my strict integrity checks enabled.

Thank you!

One additional finding:

I was able to reproduce the exact 64-byte vercel.json observed in the Vercel build environment:

1
{"git":{"deploymentEnabled":false},"name":"infoit","version":2}

Including a trailing LF newline, this produces exactly the observed SHA-256:

4cc26eab9f2cbee1bf6719e932b25c69aed623d2e80d5d40045884bd8529d586

The additional name and version fields appear consistent with Vercel's deployment configuration processing.

This suggests that vercel.json may be regenerated during build preparation, although I have not identified the process responsible.

Could you confirm whether this is expected behavior?

Thank you!