Introducing v0.5.1

On March 19, 2026, we released gcpidentitytokenportal v0.5.1, a maintenance release that brings improved user visibility and deployment simplification to your GCP identity token management workflow.

This update focuses on what matters most to operators: knowing exactly which version you’re running, and deploying with fewer moving parts. It’s a drop-in upgrade with no breaking changes—just pull the new image and you’re ready to go.

What’s New

Version Display in Web UI

For the first time, you can see exactly which version of gcpidentitytokenportal you’re running—right from the web interface. The new footer at the bottom of the page displays:

  • The application version number
  • A link to the project repository on GitHub
  • MIT License information

This simple addition helps teams quickly verify they’re running the expected version across multiple deployments without needing to check container labels or deployment manifests.

Embedded Templates for Simpler Deployment

We’ve streamlined how templates are handled in the container image. HTML templates are now embedded directly into the Go binary at compile time, eliminating the need to copy a separate templates/ directory into your runtime container.

What this means for you:

  • Fewer layers in your Docker image
  • Reduced risk of template mismatches between binary and filesystem
  • Simpler container builds with fewer COPY directives
  • A more robust single-binary distribution model

Updated Base Image: Debian 13

The runtime container has been upgraded from Debian 12 to Debian 13 (Trixie), bringing the latest security patches and system library updates at the OS level—all without any configuration changes on your end.

Go Runtime Upgrade: 1.26.1

gcpidentitytokenportal now builds with Go 1.26.1, up from 1.25.6. This upgrade includes performance improvements, compiler optimizations, and runtime bug fixes that contribute to a more reliable application experience.

Dependency Updates

Several Google Cloud client libraries have been updated to their latest versions, incorporating security patches and upstream bug fixes:

  • google.golang.org/api: 0.260.0 → 0.271.0
  • golang.org/x/oauth2: 0.34.0 → 0.36.0
  • google.golang.org/grpc: 1.78.0 → 1.79.3

Why It Matters

This release exemplifies our commitment to operational excellence. The version display feature addresses a common real-world need: teams running multiple environments (development, staging, production) can now instantly confirm version parity at a glance.

The embedded templates change may seem technical, but it has practical benefits. By reducing the number of file operations and layers in the container image, we’ve decreased the surface area for deployment issues. The single-binary model is more resilient—what you build is what you run, with no risk of template files getting out of sync.

Combined with routine updates to the Go runtime, base OS, and dependencies, v0.5.1 ensures your token portal runs on well-maintained, secure foundations without requiring any action from you beyond pulling the updated image.

Upgrade & Installation

Upgrading to v0.5.1 is straightforward and requires no configuration changes:

# Pull the new version
docker pull ghcr.io/unitvectory-labs/gcpidentitytokenportal:v0.5.1

# Or use latest if you prefer automatic updates
docker pull ghcr.io/unitvectory-labs/gcpidentitytokenportal:latest

Kubernetes Users

Update your Deployment manifest to reference the new image tag:

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

What You Don’t Need to Worry About

This upgrade is fully backward compatible. No changes are required to:

  • Environment variables (GOOGLE_APPLICATION_CREDENTIALS, PORT)
  • Volume mounts for credentials or configuration files
  • Network configuration
  • Service account permissions or Workload Identity Federation setup

Get Started

Ready to try v0.5.1? Head over to the GitHub releases page for full details, or pull the image and see the new version footer in action.

As always, gcpidentitytokenportal remains a lightweight, secure way to vend GCP identity tokens with custom audiences—whether you’re on GCP using the metadata service, outside GCP with JSON key files, or running on Kubernetes with Workload Identity Federation.

This release announcement was AI-generated using the unsloth/Qwen3.5-122B-A10B-GGUF:Q4_K_M model. It was generated based on the v0.5.1 release of UnitVectorY-Labs/gcpidentitytokenportal published on March 19, 2026. For questions or feedback, visit the release-storyteller repository.