The Wire · Showcase
VAULT JWT PLUGIN BUMPS GO TO 1.26.3, PACKER AZURE LOCKS DOWN COMPLIANCE
By RepoJournal · Filed · About HashiCorp
Vault's JWT auth plugin is shipping a toolchain upgrade while HashiCorp audits its entire plugin ecosystem for licensing compliance.
The vault-plugin-auth-jwt team pushed a Go version bump to 1.26.3 [1] [2], a routine but necessary maintenance move that keeps the auth plugin aligned with upstream security patches and performance improvements. Across the org, packer-plugin-azure just went through a compliance sweep [3] [4] [5], part of a larger HashiCorp-wide audit to ensure all plugins meet IBM's licensing standards — expect similar PRs across your plugin repos over the next few weeks. Nothing breaking here, but the JWT plugin upgrade should land before your next Vault rebuild if you're running recent Go versions in production.
Action items
- → Rebuild vault-plugin-auth-jwt with Go 1.26.3 in your next release cycle hashicorp/vault-plugin-auth-jwt [plan]
- → Review compliance PRs hitting your HashiCorp plugin repos — merge them without delay hashicorp/packer-plugin-azure [plan]
References
- [1] prepare 0.26.3 release ↗ hashicorp/vault-plugin-auth-jwt
- [2] updated go version (#392) hashicorp/vault-plugin-auth-jwt
- [3] [COMPLIANCE] Add/Update Copyright Headers ↗ hashicorp/packer-plugin-azure
- [4] Merge pull request #615 from hashicorp/compliance/add-headers hashicorp/packer-plugin-azure
- [5] [COMPLIANCE] Add/Update Copyright Headers hashicorp/packer-plugin-azure
FAQ
- What changed in HashiCorp on May 11, 2026?
- Vault's JWT auth plugin is shipping a toolchain upgrade while HashiCorp audits its entire plugin ecosystem for licensing compliance.
- What should HashiCorp teams do about it?
- Rebuild vault-plugin-auth-jwt with Go 1.26.3 in your next release cycle • Review compliance PRs hitting your HashiCorp plugin repos — merge them without delay
- Which HashiCorp repositories shipped on May 11, 2026?
- hashicorp/vault-plugin-auth-jwt, hashicorp/packer-plugin-azure