Conversation
There was a problem hiding this comment.
Pull request overview
This PR prepares the v0.13.0 release of vault-plugin-secrets-kubernetes by upgrading the Go version from 1.25.x to 1.26.1 and bumping several dependencies including vault/sdk, vault/api, go-jose, and others. The CHANGELOG is updated to document these changes.
Changes:
- Bumped Go version to 1.26.1 in
go.modand.go-version - Upgraded multiple dependencies (
vault/sdk,vault/api,go-jose,logr,oauth2,protobuf) - Added v0.13.0 entry to CHANGELOG.md
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| go.mod | Bumps Go directive to 1.26.1 and upgrades direct/indirect dependencies |
| go.sum | Updated checksums for upgraded dependencies |
| CHANGELOG.md | Added v0.13.0 release entry with dependency change summary |
| .go-version | Updated Go version from 1.25.1 to 1.26.1 |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
d0bd07e to
7d7f7a5
Compare
7d7f7a5 to
77277f3
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
| module github.com/hashicorp/vault-plugin-secrets-kubernetes | ||
|
|
||
| go 1.25.0 | ||
| go 1.26.1 |
| ### March 16, 2026 | ||
|
|
||
| Update dependencies (#123): | ||
| * go 1.25.0 => 1.26.1 |
Overview
The PR upgrades dependencies and go version and prepares CHANGELOG for v0.13.0 release.
$ scratch/tag_info.sh
$ make dev && scan binary ./bin/vault-plugin-secrets-kubernetes
$ make test
make integration-test
Related Issues/Pull Requests
[ ] Issue #1234
[ ] PR #1234
Contributor Checklist
[ ] Add relevant docs to upstream Vault repository, or sufficient reasoning why docs won’t be added yet
My Docs PR Link
Example
[ ] Add output for any tests not ran in CI to the PR description (eg, acceptance tests)
[ ] Backwards compatible
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.