I would consider this a case of "expectation management"-based versioning. This is a release designed to keep Gemini in the news cycle, but it isn't a significant enough improvement to justify calling it Gemini 3.0.
If you could get much better performance without changing the algorithm (eg just by scaling), you'd still bump the number.