Introduction

We’re pleased to announce the release of GCP Identity Token Portal v0.4.0, published on January 26, 2025. This maintenance release focuses on improving build reliability and keeping dependencies up to date, ensuring a more robust experience for all users deploying the portal in production environments.

While this version doesn’t introduce new features, it represents our ongoing commitment to code quality, build best practices, and maintaining alignment with the latest Google API client libraries.

What’s New

Improved Build Reliability

The Docker build pipeline has been enhanced to produce statically linked binaries. This change eliminates dynamic library dependencies within the container, resulting in:

  • Better compatibility across different Linux distributions and base images
  • Reduced potential runtime issues related to missing shared libraries
  • A more portable and predictable deployment artifact

For teams running GCP Identity Token Portal in Kubernetes or on Cloud Run, this means one less thing to worry about during deployment.

Updated Dependencies

We’ve updated the Google API Go client library (google.golang.org/api) from version 0.217.0 to 0.218.0. This routine dependency update brings:

  • Upstream bug fixes from the Google APIs team
  • Improved error handling for resumable uploads
  • Alignment with the latest discovery clients for various Google APIs

Keeping dependencies current ensures you benefit from upstream security patches and improvements without additional effort on your part.

Module Path Standardization

The Go module path has been updated to use the full GitHub repository path (github.com/UnitVectorY-Labs/gcpidentitytokenportal). This change follows Go best practices and makes the module path unambiguous for anyone importing this project as a library in their own applications.

Why It Matters

Maintenance releases might not grab headlines, but they’re essential for long-term software health. Here’s why v0.4.0 matters to you:

Production Confidence: Statically linked binaries mean your containers will behave consistently regardless of the underlying host environment. Whether you’re deploying to Google Cloud Run, a Kubernetes cluster, or any container runtime, you can trust that the binary has everything it needs built-in.

Security and Stability: By staying current with Google’s API client libraries, you’re automatically incorporating upstream security fixes and bug resolutions. This proactive approach reduces your exposure to known issues without requiring urgent patch deployments.

Future-Proofing: Standardizing on proper module paths sets the project up for clean growth and makes it easier for contributors and library consumers to work with the codebase correctly from the start.

Upgrade Instructions

For Docker and Container Users

Upgrading is straightforward—just update your image tag:

docker run --name gcpidentitytokenportal -d -p 8080:8080 \
  -v /path/to/your-service-account-key.json:/creds.json \
  -v /path/to/your-config.yaml:/config.yaml \
  -e GOOGLE_APPLICATION_CREDENTIALS=/creds.json \
  ghcr.io/unitvectory-labs/gcpidentitytokenportal:v0.4.0

No configuration changes are required. All settings from v0.3.x remain fully compatible.

For Kubernetes Deployments

Update the image reference in your deployment manifests:

spec:
  containers:
    - name: gcpidentitytokenportal
      image: ghcr.io/unitvectory-labs/gcpidentitytokenportal:v0.4.0

For Library Consumers

If you’re importing GCP Identity Token Portal as a Go library in your own project, you’ll need to update your import paths:

// Before (v0.3.x)
import "gcpidentitytokenportal/internal/..."

// After (v0.4.0)
import "github.com/UnitVectorY-Labs/gcpidentitytokenportal/internal/..."

Transparency Note

This release announcement was AI-generated using the unsloth/Qwen3.5-122B-A10B-GGUF:Q4_K_M model. The information presented is based on the actual code changes and release data from the UnitVectorY-Labs/gcpidentitytokenportal repository, specifically the v0.4.0 release published on January 26, 2025.

Generated by release-storyteller.