Hey there! Great question. Let me break this down clearly for you:

As of now, Google Cloud Endpoints fully supports OpenAPI 3.0 — so you don’t have to wait for a "planned" rollout anymore. Here’s what you need to know:

• You can define your APIs using the OpenAPI 3.0 specification and deploy them directly to Endpoints, just like you would with the 2.0 version.
• Core features you’d rely on (like API key validation, OAuth2 integration, rate limiting) all work seamlessly with 3.0 definitions.
• OpenAPI 3.0 brings useful improvements over 2.0, such as better component reuse, more flexible parameter schemas, and support for modern API design patterns. If you’re still using 2.0, migrating is totally feasible and worth considering for these benefits.

Just a quick heads-up: Make sure your OpenAPI 3.0 YAML/JSON file adheres to Endpoints-specific extensions (like x-google-* fields) where needed — the official docs outline these requirements clearly if you need a reference.

Pro tip: If you hit deployment snags, double-check that you’re using the latest version of the Endpoints deployment tools, as older versions might not handle 3.0 definitions correctly.

内容的提问来源于stack exchange，提问作者Emile