Issue Deploying from Private GitHub Organization-Owned Repo

So I just tried to deploy to Vercel via a push to my GitHub repo and got an email along the lines of the idea below:

We were unable to deploy a commit from a private repository on your GitHub organization to the Shigeo team, which is currently on the Hobby plan.

Is this a recent change in Vercel's policies for Hobby accounts trying to deploy from a private GitHub repo from a GitHub organization? I was able to push and deploy just 12 hours ago so this must've been implemented within that time frame, unless there is some deeper issue.

I tried looking around online for policy changes made in the past 24 hours (looked at the blog, changelog, etc). I do see some similar posts in the forum from around July, but nothing from the past 24 hours.

Hey, Jeffrey! Welcome to the Vercel Community

From the relevant docs:

The Hobby Plan does not support collaboration for private repositories. If you need collaboration, upgrade to the Pro Plan.

To deploy commits under a Hobby team, the commit author must be the owner of the Hobby team containing the Vercel project connected to the Git repository. This is verified by comparing the Login Connections Hobby team's owner with the commit author.

So this limitation has been in place for a while. Nothing changed in the last 24 hours. If things were working just 12 hours ago, that usually points to one of these scenarios:

Repository ownership: The repo may have recently been moved to an organization, or organization permissions might have changed.
Team plan status: Double-check your Vercel team’s plan in the dashboard to confirm you’re still on Hobby.
Repository visibility: Make sure the repo is still private and organization-owned.

To get things deploying again, you can:

Upgrade to a Pro plan to continue using private organization repositories
Transfer the repo to your personal GitHub account (if that fits your workflow)
Make the repo public if open-sourcing is an option

Let us know if you have any more questions!