Skip to content

chore(release): pin redisconn providers to redisconn v0.0.4 - #384

Merged
aponcedeleonch merged 1 commit into
mainfrom
release/pin-providers-redisconn-v0.0.4
Oct 15, 2026
Merged

aponcedeleonch merged 1 commit into
mainfrom
release/pin-providers-redisconn-v0.0.4

Conversation

@aponcedeleonch

Copy link
Copy Markdown
Member

Summary

  • The go-redis v9.23.0 bump (Update module github.com/redis/go-redis/v9 to v9.23.0 #314) landed after v0.0.54 and touched redisconn plus all three provider modules. A root release from current main fails scripts/validate-release.sh because those modules changed since their tags.
  • Following the staged order in docs/redisconn-extraction.md, redisconn/v0.0.4 is tagged from main (964aa6a). Both the manual preflight and the tag-triggered Release run passed. This PR points the provider modules at it.

Next steps after merge

  1. Tag this merge commit as redisconn/aws/v0.0.8, redisconn/azure/v0.0.6 and redisconn/gcp/v0.0.4.
  2. Pin the root go.mod to the four new versions.
  3. Tag the root v0.0.55.

Please hold Renovate PRs that touch redisconn* until this finishes. They would make the new tags stale again.

Type of change

  • Other: release preparation

Test plan

  • ./scripts/validate-release.sh redisconn/v0.0.4 passed on 964aa6a before tagging.
  • GOWORK=off go mod tidy, go mod verify, go build ./..., go vet ./... and go test -race ./... in each provider module. Tidy produced no further changes.
  • ./scripts/check-redisconn-modules.sh passed.

🤖 Generated with Claude Code

The go-redis v9.23.0 bump (#314) touched redisconn and all three
provider modules after their last tags, so a root release from main
fails validation. redisconn/v0.0.4 is now tagged from main (964aa6a).
Point the provider modules at it so they can be tagged next.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@aponcedeleonch
aponcedeleonch merged commit 3c98451 into main Oct 15, 2026
6 checks passed
@aponcedeleonch
aponcedeleonch deleted the release/pin-providers-redisconn-v0.0.4 branch October 15, 2026 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants