Skip to content

Conversation

brandur
Copy link
Member

@brandur brandur commented Aug 2, 2020

Reverts the upgrade to go-redis v8 that I made a few days ago because in
retrospect, it seems likely to cause more problems than it solves.

I'd thought that going to v8 was somewhat unpreventable because it was
their master branch, but the main problem seems to have been that this
project was not on Go Modules. Now that it is, go-redis v6 gets pulled
by default, and an explicit major needs to be specified to get anything
later.

Also, according to the go-redis CHANGELOG, v8 is not yet released.

I'm not sure what the best course of action is going forward, but it may
be that we should release new stores to support new majors from the
supported adapters. There may be a better way, but I'm not sure what it
is yet.

Reverts the upgrade to go-redis v8 that I made a few days ago because in
retrospect, it seems likely to cause more problems than it solves.

I'd thought that going to v8 was somewhat unpreventable because it was
their `master` branch, but the main problem seems to have been that this
project was not on Go Modules. Now that it is, go-redis v6 gets pulled
by default, and an explicit major needs to be specified to get anything
later.

Also, according to the go-redis CHANGELOG, v8 is not yet released.

I'm not sure what the best course of action is going forward, but it may
be that we should release new stores to support new majors from the
supported adapters. There may be a better way, but I'm not sure what it
is yet.
@brandur brandur force-pushed the brandur-revert-v8-upgrade branch from 1fb8e71 to 7ad8a69 Compare August 2, 2020 01:20
@brandur brandur merged commit 683dfd6 into master Aug 2, 2020
@brandur brandur deleted the brandur-revert-v8-upgrade branch August 2, 2020 01:22
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.

1 participant