Deployment starts even when a non-member account commits to git in the Pro plan.
This never happened before, but now when I commit to git, even with a non-member account, it starts deploying. deploying works in the preview environment, but not the behavior I expect.
Hi,
Can you share an example commit SHA (40 characters) for one of the affected commit so we can take a look?
1 Like
Hi,
I copied it from my github.
75513ef4007e259475e7605f75a7cbd6a9c221e5
1 Like
Thanks! I checked our logs and noticed I don’t see any deployment for this commit:
Received deployment final event of type “deployment-error” . The commit author (hiro***) is not a bot and not a team member but the owner is a team (team_bnRQxcP***********) and the deploy does require NSNB to pass
Do you have a deployment ID where you see this commit to be deployed? You can visit Vercel dashboard and click on the specific deployment to find the deploy id (in URL bar)
1 Like
The Vercel page shows something like “h3hsphen4” as an ID.
In the URL we found the string “HbucuZ7cRkJFALyojFQBMGpTyXjd”.
1 Like
Thank you for sharing details! We are investigating this!
1 Like
We released a fix which should prevent this I believe. Can you monitor and let me know if you can still reproduce this?
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.