Which version of core ends up in your lockfile? @GoogleDevelopers
Which version of core ends up in your lockfile? @GoogleDevelopers
Uploaded August 2026 | Updated September 2026, 1 week ago
A dependency resolution puzzle about a failure mode that hides from normal debugging.
Three packages share a single dependency, and each declares its own version constraint. Checked in pairs, every combination is compatible. The question is what happens when all three are installed together. Watch the clip and comment: which version of the shared dependency gets installed?

Subscribe to Google for Developers → https://goo.gle/developers

Speakers: Jasmyne Roberts
Which version of core ends up in your lockfile?Build voice-first apps with Gemini 3.5 TranscribeGive your Gemini Live Agent a phone number!From prompt to a fully working real-time voice app in seconds. 🎙️✨Ok, I guess the rain is asking us real questions now.When the warm-up routine is a little excessive.Stop writing longer prompts. Do this instead! 🧠Face Control AI at Google I/O 2024What’s new in Android (Google I/O 2026 recap)Visualizing Text-Only Menus with Images with Nano Banana ProInside YC x Google DeepMind Startups DayWhat is Gemini 3.7 Flash?
Google for Developers |

Which version of core ends up in your lockfile?

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER