Skip to content

2.2.0 upgrade backwards incompatible (loses data) #469

@henrik

Description

@henrik

It looks like our running tests were reset when we upgraded from 2.1.0 to 2.2.0, though the changelog or version numbers did not suggest backwards incompatibility.

A hypothesis is that removing Redis namespace as a dependency also changed the Redis keys so Split stopped using old keys and made new ones instead. Have not investigated this a lot, but glancing at Redis keys, this seems like it could be the case.

If you think this is correct, maybe the README could include a backwards-compatibility warning for this version?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions