GitHub ships Gemini 4 Neon, eight new Copilot connectors, and automatic security scans for Team orgs
GitHub turned on free security risk scanning by default for every organization on its Team plan on November 18, the same day it widened what Copilot can connect to and run: a new model, eight fresh service connectors, and a way to push shared plugins to an entire team at once.
What happened
Four separate changelog entries landed on November 18. Security risk assessments now run automatically for organizations on GitHub Team, surfacing exposed credentials and code vulnerabilities for admins and security managers to review. That scan was already free for Team and Enterprise orgs as a self-serve tool, per GitHub's documentation; running it no longer requires anyone to ask. Gemini 4 Neon became generally available as a selectable Copilot model, billed at provider list pricing under usage-based billing and rolling out to Pro+, Max, Business, and Enterprise users across VS Code, Visual Studio, Copilot CLI, the Copilot coding agent, JetBrains, Xcode, Eclipse, and github.com. Per Google, it matches Gemini 4 Carbon's quality at a lower token cost, starts responding faster, and makes fewer unrequested changes on coding tasks. Copilot also gained eight new connectors, Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow, and Wix, joining more than 25 services already available, in public preview across every Copilot plan. And organization teams can now set shared plugin defaults through a new "Customize Copilot" tab, generally available on Business and Enterprise.
Four admin decisions landed on the same day
None of these four changes needs an admin to act before taking effect, and that is the catch. The security risk assessment is already scanning Team orgs and will surface findings whether or not anyone asked for them, so a security manager who has not checked the dashboard could already be sitting on an unreviewed report of exposed secrets. Public preview covers all eight new connectors on every plan, but Business and Enterprise admins who allowlist MCP connectors individually rather than by wildcard need to add each one by hand or their users will not see them, per GitHub's enterprise allowlist documentation. Gemini 4 Neon is on by default too: per the changelog, new models are automatically enabled under default model enablement unless an admin has turned off the global default or blocked that specific model. Team plugin defaults are the one opt-in piece, since a team maintainer has to pick plugins before members see them, but once chosen those plugins turn on for direct team members without anyone repeating setup, and child teams do not inherit them automatically.
What to watch next
GitHub has not said whether the connector roster will keep expanding at this pace or whether Gemini 4 Neon's gradual rollout will reach every listed surface on the same schedule. The more pressing item for admins is the security risk assessment: now that it runs without a request, the open question is how much time GitHub expects Team orgs to take acting on findings before the next automated scan adds to the pile.
Sources
- Gemini 4 Neon in GitHub Copilot: GitHub changelog, November 18, 2026
- Connect Supabase, Box, Calendly, and more to Copilot: GitHub changelog, November 18, 2026
- Security risk assessments run automatically on GitHub Team: GitHub changelog, November 18, 2026
- Customize GitHub Copilot for your team: GitHub changelog, November 18, 2026
