chore(db): Squash old migrations into a single file #3829
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8004fe5 to
9aea9ff
Compare
groyoh
approved these changes
Jun 13, 2025
|
Shouldn't the |
@groyoh, no, we actually don't want it to be impacted, the |
f20ee96 to
2d76947
Compare
2d76947 to
4f4b150
Compare
rsempe
added a commit
that referenced
this pull request
Jun 17, 2025
Reverts #3829 We want to exclude that from the `1.30` self-hosted release. Will be included on the `1.31` release.
vincent-pochet
added a commit
that referenced
this pull request
Jun 26, 2025
…#3842) Reapply #3839 that was rollbacked to allow a non blocking release ## Context As we are planing to release the ["not null organization" pull request](#3687), it was decided to take this as an opportunity to squash the old database migration into a single migration file, to reduce the number of migrations. Related to #3829 ## Description Lago version 1.20.0 was used as a reference to squash the migrations. - All migrations from previous versions are merged in a single `InitialMigration` migration file. - It uses the SQL format to preserve the orders and make sure the migration test workflow continue to pass on Github no matter if the structure comes from previous migrations or from this file. - It reuse the previous last migration version `20250122112050` to make sure it will not be executed on instance running v1.20.0 or later. - It adds a small check to fail running the migration if an upgrade is made from a version prior to 1.20.0 to the bridge release containing this change - All squashed migrations files are removed
diegocharles
pushed a commit
that referenced
this pull request
Jun 30, 2025
…#3842) Reapply #3839 that was rollbacked to allow a non blocking release ## Context As we are planing to release the ["not null organization" pull request](#3687), it was decided to take this as an opportunity to squash the old database migration into a single migration file, to reduce the number of migrations. Related to #3829 ## Description Lago version 1.20.0 was used as a reference to squash the migrations. - All migrations from previous versions are merged in a single `InitialMigration` migration file. - It uses the SQL format to preserve the orders and make sure the migration test workflow continue to pass on Github no matter if the structure comes from previous migrations or from this file. - It reuse the previous last migration version `20250122112050` to make sure it will not be executed on instance running v1.20.0 or later. - It adds a small check to fail running the migration if an upgrade is made from a version prior to 1.20.0 to the bridge release containing this change - All squashed migrations files are removed
diegocharles
pushed a commit
that referenced
this pull request
Jul 11, 2025
## Context As we are planing to release the ["not null organization" pull request](#3687), it was decided to take this as an opportunity to squash the old database migration into a single migration file, to reduce the number of migrations. Related to #3829 ## Description Lago version 1.20.0 was used as a reference to squash the migrations. - All migrations from previous versions are merged in a single `InitialMigration` migration file. - It uses the SQL format to preserve the orders and make sure the migration test workflow continue to pass on Github no matter if the structure comes from previous migrations or from this file. - It reuse the previous last migration version `20250122112050` to make sure it will not be executed on instance running v1.20.0 or later. - It adds a small check to fail running the migration if an upgrade is made from a version prior to 1.20.0 to the bridge release containing this change - All squashed migrations files are removed
diegocharles
pushed a commit
that referenced
this pull request
Jul 11, 2025
Reverts #3829 We want to exclude that from the `1.30` self-hosted release. Will be included on the `1.31` release.
diegocharles
pushed a commit
that referenced
this pull request
Jul 11, 2025
…#3842) Reapply #3839 that was rollbacked to allow a non blocking release ## Context As we are planing to release the ["not null organization" pull request](#3687), it was decided to take this as an opportunity to squash the old database migration into a single migration file, to reduce the number of migrations. Related to #3829 ## Description Lago version 1.20.0 was used as a reference to squash the migrations. - All migrations from previous versions are merged in a single `InitialMigration` migration file. - It uses the SQL format to preserve the orders and make sure the migration test workflow continue to pass on Github no matter if the structure comes from previous migrations or from this file. - It reuse the previous last migration version `20250122112050` to make sure it will not be executed on instance running v1.20.0 or later. - It adds a small check to fail running the migration if an upgrade is made from a version prior to 1.20.0 to the bridge release containing this change - All squashed migrations files are removed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
As we are planing to release the "not null organization" pull request, it was decided to take this as an opportunity to squash the old database migration into a single migration file, to reduce the number of migrations.
Related to #3829
Description
Lago version 1.20.0 was used as a reference to squash the migrations.
InitialMigrationmigration file.20250122112050to make sure it will not be executed on instance running v1.20.0 or later.