[agentic-release]

Automated release-prep PR raised by the Release Preparation Agent.

Release details

• Version: 0.14.5
• Repository: hashicorp/vault-lambda-extension
• Raised on behalf of: 6470001FPZ

Steps completed by the agent

• ✅ GitHub milestone created/confirmed
• ✅ Repository cloned locally
• ✅ Repo-specific steps: none (no agent-config.yaml steps)
• ✅ Go toolchain and dependencies updated
• ✅ CVE scan: 0 critical, 6 high ⚠️
• ✅ CHANGELOG.md updated (2 PR(s) included: Update Go version to 1.27.1 and bump dependencies. #198, Bump github.com/go-jose/go-jose/v3 from 3.0.4 to 3.0.5 in /quick-start/demo-function #199)

What to do next

1. Review this PR and the CHANGELOG.md changes
2. Verify the build.yaml acceptance test matrix includes the new Vault versions
3. Check the milestone — move any unready issues to the next milestone
4. Approve and merge this PR
5. The Release Agent will then cut the release tag and promote to staging

[Balaji2198]

For the Vault Lambda Extension, the DEPENDENCIES section doesn't appear to be used in the changelog. Could we move all dependency updates under the IMPROVEMENTS section for consistency with previous releases?