Good question. There is now IApiVersioningBuilder that all subsequent configurations and services hang off of. The idea was to centralize everything API Versioning via one builder. Previously, there were several different configuration paths.

You have the correct package. The setup should now be:

builder.Services.AddApiVersioning()
 .AddApiExplorer(options => GroupNameFormat = "'v'VVV");

This configuration will implicitly imply:

builder.Services.AddApiVersioning()
 .AddMvc() // ← adds MVC Core with versioning support for controllers
 .AddApiExplorer(options => GroupNameFormat = "'v'VVV");

With the introduction of Minimal APIs, AddApiVersioning() doesn't all the services you'll need. IApiVersioningBuilder.AddMvc() brings in the MVC Core features for controllers, but not the full MVC stack (which has confused some people). IApiVersioningBuilder.AddApiExplorer will implicitly bring in the necessary services if you haven't already. The Versioned part of the name was dropped to make it more succinct and is unambiguous since it is directly associated with the IApiVersioningBuilder.