Introduction

On October 17, 2024, we released version 0.2.0 of authzjwtbearerinjector. This maintenance release focuses on internal improvements and dependency updates that strengthen the foundation for future development while maintaining complete backward compatibility with v0.1.1.

authzjwtbearerinjector is a gRPC-based ExtAuthz service for Envoy Proxy that implements the JWT Bearer flow to inject authentication credentials into backend services. This latest release ensures you’re running with the latest dependency versions and benefits from improved code maintainability that will accelerate future feature development.

What’s New

Version 0.2.0 is a maintenance release with no new user-facing features. However, it includes several important internal improvements:

Dependency Updates

  • Updated go-control-plane library from v0.13.0 to v0.13.1 for enhanced compatibility with Envoy Proxy’s control plane

Security Enhancements

  • Added CodeQL Advanced security scanning to our CI/CD pipeline for continuous code security analysis
  • Upgraded Docker metadata-action to v5 for improved container image metadata handling

Codebase Improvements

  • Restructured internal Go packages for better maintainability and organization (cache, config, jwt, logger, oauth, rsa)
  • Added 30-minute timeouts to CI/CD workflows to prevent stale builds

Why It Matters

While this release doesn’t introduce new features, it serves an important purpose:

Security First: The updated go-control-plane dependency brings the latest security patches and improvements from the Envoy Proxy ecosystem. Combined with our new CodeQL scanning, you can trust that authzjwtbearerinjector maintains a strong security posture.

Foundation for Growth: The internal package restructuring may not be visible to you, but it significantly improves how we maintain and develop the project. This cleaner architecture will enable faster delivery of future features in upcoming releases.

Zero Downtime: Because there are no behavioral changes, upgrading is completely safe. You can deploy v0.2.0 without any configuration modifications or operational disruption.

Upgrading to v0.2.0

Upgrading is straightforward—no configuration changes required:

Docker

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

Kubernetes

Update your deployment image reference:

spec:
  containers:
  - name: authzjwtbearerinjector
    image: ghcr.io/unitvectory-labs/authzjwtbearerinjector:v0.2.0

All existing configuration options, environment variables, and Envoy route metadata settings continue to work exactly as before. Your service will operate identically with the improved internal architecture and updated dependencies.

This post was AI-generated by unsloth/Qwen3.5-122B-A10B-GGUF:Q4_K_M. For more information, visit the repository or view the v0.2.0 release. Generated by release-storyteller.