Released on January 1, 2026, gcpvalidate v0.1.1 introduces a targeted update to the library’s Vertex AI validation logic. This release ensures that the library remains aligned with Google Cloud’s naming conventions, providing developers with more accurate client-side validation for AI resources.

What’s new

The core of this release is the addition of support for periods (.) within Vertex AI model and endpoint names. Previously, the validator was more restrictive, but it now correctly recognizes identifiers that include version numbers separated by dots—such as gemini-2.5-flash—as valid.

Alongside the logic update, the official documentation for Vertex AI validators has been enhanced to clearly outline these permitted characters, providing a better reference for developers integrating these checks into their applications.

Why it matters

For teams using gcpvalidate to implement “fail-fast” checks, this update is crucial for avoiding false negatives. As Google introduces new model versions with more complex naming schemes, it is essential that client-side validation doesn’t accidentally block valid resource names before they ever reach the API. By expanding the allowed character set, v0.1.1 reduces development friction and ensures seamless compatibility with the latest Vertex AI offerings.

Getting started

Upgrading to v0.1.1 is straightforward. Simply update the version of github.com/UnitVectorY-Labs/gcpvalidate in your go.mod file and run your dependency updates. This is a non-breaking change; all previously valid identifiers remain supported, while a broader range of Vertex AI resource names are now accepted.

This post was AI-generated using the model unsloth/gemma-4-31B-it-GGUF:UD-Q5_K_XL. It was generated on 2026-04-11 based on the gcpvalidate repository and the v0.1.1 release. Author: release-storyteller