On October 17, 2024, we released v0.2.0 of authzjwtbearerinjector. This update is a dedicated maintenance release focused on improving the internal structure and security posture of the service, ensuring a more stable and maintainable foundation for future growth.

What’s new

This release focuses on “under-the-hood” improvements rather than new feature flags:

  • Architectural Refactoring: We have reorganized the internal codebase, splitting the monolithic internal package into dedicated modules for caching, configuration, JWT handling, logging, OAuth communication, and RSA operations.
  • Dependency Updates: The service has been updated to use go-control-plane v0.13.1.
  • Enhanced Security Pipeline: We integrated CodeQL analysis into our GitHub Actions workflow to provide automated security scanning for every change.

Why it matters

While this release doesn’t change how you configure the service, these improvements are vital for the long-term health of the project. Moving to a modular architecture reduces technical debt and allows us to develop new capabilities more rapidly. Furthermore, the introduction of automated security scanning adds an essential layer of protection, ensuring the reliability of the JWT-bearer flow in production environments.

Upgrade and Installation

Upgrading to v0.2.0 is straightforward. Simply pull the latest Docker image from the GitHub Container Registry: ghcr.io/unitvectory-labs/authzjwtbearerinjector.

This release is fully backward compatible; no changes to your Envoy Proxy route metadata, environment variables, or YAML configurations are required.

This post was AI-generated using the model unsloth/gemma-4-31B-it-GGUF:UD-Q5_K_XL. It was generated on 2026-04-09 based on the v0.2.0 release of the UnitVectorY-Labs/authzjwtbearerinjector repository. Author: release-storyteller