Introduction

On January 26, 2025, UnitVectorY-Labs released v0.3.0 of authzjwtbearerinjector, a gRPC-based ExtAuthz service for Envoy Proxy that implements the JWT-bearer flow for injecting authentication credentials to backend services. This release represents a structural improvement to how the project is consumed as a Go module, aligning with community best practices for public Go repositories.

What’s New

The v0.3.0 release introduces a single but important change: the Go module path has been updated from authzjwtbearerinjector to github.com/UnitVectorY-Labs/authzjwtbearerinjector. This update brings the project in line with standard Go module conventions for GitHub-hosted repositories.

Key Changes

  • Updated module path: The Go module now uses the full GitHub organization path (github.com/UnitVectorY-Labs/authzjwtbearerinjector)
  • No functional changes: This release contains no changes to the service’s behavior, API, or configuration options
  • Transparent for most users: Users consuming authzjwtbearerinjector via Docker container or binary experience no impact

Why It Matters

Standardizing the module path on the GitHub organization URL improves the developer experience in several ways:

  1. Better discoverability: The full GitHub path makes it immediately clear where the project is hosted
  2. Go proxy compatibility: Follows established conventions that Go tooling expects for public modules
  3. Clear provenance: Import paths now directly reference the source repository location

This change follows Go community best practices for organizing and publishing open-source Go packages.

Breaking Change Notice

For Go developers directly importing this package as a library, import paths must be updated:

// Before v0.3.0
import authz_cache "authzjwtbearerinjector/internal/cache"

// v0.3.0 and later
import authz_cache "github.com/UnitVectorY-Labs/authzjwtbearerinjector/internal/cache"

Note: If you’re running authzjwtbearerinjector as a sidecar service via Docker or binary (the primary intended usage pattern), no changes are required. The gRPC interface and configuration remain completely unchanged.

Upgrade and Installation

For Container/Binary Users (No Action Required)

If you’re using the pre-compiled Docker image or binary, you can continue using v0.3.0 without any modifications:

docker pull ghcr.io/unitvectory-labs/authzjwtbearerinjector:v0.3.0

For Go Library Users

To upgrade to v0.3.0 or later:

go get github.com/UnitVectorY-Labs/authzjwtbearerinjector@v0.3.0

Then update all import statements throughout your codebase from authzjwtbearerinjector/... to github.com/UnitVectorY-Labs/authzjwtbearerinjector/....

Recommendation

Since v0.3.0 was released on the same day as v0.2.3 and subsequent releases contain additional improvements (including statically linked binaries in v0.3.1), consider upgrading directly to v0.3.1 or later for the most stable experience.

This post was AI-generated using the unsloth/Qwen3.5-122B-A10B-GGUF:Q4_K_M model. For more details about this release, visit the authzjwtbearerinjector GitHub repository and the v0.3.0 release page. Article generated by release-storyteller.