Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apply migrations in the proper order #4913

Closed
jgsogo opened this issue Apr 5, 2019 · 0 comments
Closed

Apply migrations in the proper order #4913

jgsogo opened this issue Apr 5, 2019 · 0 comments

Comments

@jgsogo
Copy link
Contributor

jgsogo commented Apr 5, 2019

Currently, migrations are being applied in reverse order. They should be applied from the lowest version to the higher one, so each migration is applied on top of all the previous ones (probably related with this bug: #4866)

        if old_version < Version("0.25"):
            ...

        if old_version < Version("1.0"):
            _migrate_lock_files(self.cache, self.out)

        if old_version < Version("1.12.0"):
            migrate_plugins_to_hooks(self.cache)

        if old_version < Version("1.13.0"):
            # MIGRATE LOCAL CACHE TO GENERATE MISSING METADATA.json
            _migrate_create_metadata(self.cache, self.out)

        if old_version < Version("1.14.0"):
            migrate_config_install(self.cache)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants