Remove DoctrineMigrationsBundle#1640
Merged
javiereguiluz merged 1 commit intosymfony:mainfrom Feb 2, 2026
Merged
Conversation
Spomky
approved these changes
Jan 27, 2026
Member
|
I agree. The most critical feature of this demo project is to provide a no-friction experience. So, we'll always provide an SQLite database ready to be used. No need to provide migrations to end users and ask them to migrate the database. |
5b16826 to
3d72dd8
Compare
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
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.
The DoctrineMigrationsBundle was originally installed as part of the symfony/orm-pack and later unpacked.
AFAIK it was never really used and there is no plan to start using it for database migrations.
So instead of upgrading to DoctrineMigrationsBundle v4 l propose to remove the unneeded dependencies.