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

feat: migrates from 0.6.7 to 1.2.0 #878

Merged

Conversation

kentbull
Copy link
Contributor

Add database migrations for:

  • 0.6.7 (Jun 16, 2022) -> 0.6.8 (Nov 2, 2022): hab_data_rename (new)
  • 0.6.8 (Nov 2, 2022) -> 1.0.0 (Mar 31, 2023): add_key_and_reg_state_schemas (new)
  • 1.0.0 (Mar 31, 2023) -> 1.2.0 (Oct 4, 2024): rekey_habs (already existed)

I discovered the need for the hab_data_rename migration while testing migration for 0.6.7 test Root GAR databases similar to production as we believe v0.6.7 is what is in production for Root GARs.

The add_key_and_reg_state_schemas we initially thought was specific to Provenant yet in my testing it turns out it is needed to take a Root GAR 0.6.7 database up to 1.0.0, so not specific to Provenant.

The rekey_habs migration was relabeled from a 1.1.0 migration to be a 1.2.0 migration since it is not applicable to the 1.1.x branch of releases and only applies to the 1.2.0 releases, and main, onwards.

@kentbull kentbull force-pushed the database-migrations-0_6_8-to_1_2_0 branch 2 times, most recently from a0887ac to 077cbc3 Compare October 14, 2024 20:17
This includes migrations 0.6.8, 1.0.0, and changes the 1.1.0 rekey_habs to 1.2.0 for clarity
@kentbull kentbull force-pushed the database-migrations-0_6_8-to_1_2_0 branch from 077cbc3 to fd10485 Compare October 14, 2024 21:10
@pfeairheller pfeairheller merged commit bce0808 into WebOfTrust:main Nov 18, 2024
6 checks passed
@kentbull kentbull deleted the database-migrations-0_6_8-to_1_2_0 branch November 25, 2024 22:28
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