Improve migrations and add support for plugins #1349

New Issue

OVERLORD · 2026-02-06T20:50:10+03:00

OVERLORD commented

2026-02-06 20:50:10 +03:00

Originally created by @mark-monteiro on GitHub (Mar 8, 2020).

Load migrations via reflection instead of hard-coding them into the migration runner. A timestamp property will need to be added to each migration and the migration runner updated to sort the migrations by timestamp in order to define the order that the migrations are run.
Prefix each migration file name with the same timestamp as used in the property. This will keep the migrations sorted in the correct order when displayed in the filesystem, IDEs etc.
Update migration runner to also log the migration namespace along side the name when executing migrations. This will be helpful when executing migrations from multiple plugins.
Migration running logic should be in Emby.Server.Implementations instead of Jellyfin.Server
Instantiate each migration using the dependency injection framework instead of manually. This way each routine can specify its own dependencies independently and it will also not be necessary to pass ApplicationHost or ILogger instances to the Run() method (#2900)

Originally created by @mark-monteiro on GitHub (Mar 8, 2020). - [ ] Load migrations via reflection instead of hard-coding them into the migration runner. A timestamp property will need to be added to each migration and the migration runner updated to sort the migrations by timestamp in order to define the order that the migrations are run. - [ ] Prefix each migration file name with the same timestamp as used in the property. This will keep the migrations sorted in the correct order when displayed in the filesystem, IDEs etc. - [ ] Update migration runner to also log the migration namespace along side the name when executing migrations. This will be helpful when executing migrations from multiple plugins. - [ ] Migration running logic should be in `Emby.Server.Implementations` instead of `Jellyfin.Server` - [x] Instantiate each migration using the dependency injection framework instead of manually. This way each routine can specify its own dependencies independently and it will also not be necessary to pass `ApplicationHost` or `ILogger` instances to the `Run()` method (#2900)

OVERLORD added the enhancement backend good first issue labels 2026-02-06 20:50:10 +03:00

OVERLORD commented

2026-02-06 20:50:12 +03:00

@sevenrats commented on GitHub (Oct 4, 2023):

@mark-monteiro what is the status of this issue?

@sevenrats commented on GitHub (Oct 4, 2023): @mark-monteiro what is the status of this issue?

OVERLORD commented

2026-02-06 20:50:14 +03:00

@mark-monteiro commented on GitHub (Oct 5, 2023):

@sevenrats Have not worked on any of the remaining tasks here and do not have time any more to work on this.

I created this issue when the migration framework was first implemented and had some ideas of how it could be improved. I'm not sure how much demand there actually is for migration support in plugins, I don't think it's something that has really come up. I would be okay if this was closed, I'll leave it up to the triage team.

@mark-monteiro commented on GitHub (Oct 5, 2023): @sevenrats Have not worked on any of the remaining tasks here and do not have time any more to work on this. I created this issue when the migration framework was first implemented and had some ideas of how it could be improved. I'm not sure how much demand there actually is for migration support in plugins, I don't think it's something that has really come up. I would be okay if this was closed, I'll leave it up to the triage team.

OVERLORD commented

2026-02-06 20:50:15 +03:00

@Bond-009 commented on GitHub (Oct 11, 2023):

This looks easy enough

@Bond-009 commented on GitHub (Oct 11, 2023): This looks easy enough

OVERLORD commented

2026-02-06 20:50:17 +03:00

@srcrist commented on GitHub (Oct 19, 2023):

@Bond-009 Were you interested in working on this? Should it be moved to "todo"?

@srcrist commented on GitHub (Oct 19, 2023): @Bond-009 Were you interested in working on this? Should it be moved to "todo"?

OVERLORD commented

2026-02-06 20:50:17 +03:00

@LezardSC commented on GitHub (Nov 28, 2025):

Hi, I'm searching for a not too hard issue to start working on the project. Is this issue still valid? If yes, I would love to give it a try.

@LezardSC commented on GitHub (Nov 28, 2025): Hi, I'm searching for a not too hard issue to start working on the project. Is this issue still valid? If yes, I would love to give it a try.

OVERLORD commented

2026-02-06 20:50:18 +03:00

@mark-monteiro commented on GitHub (Dec 9, 2025):

@LezardSC I haven't been involved in the project in a while so I'm not 100% sure, but as far as I know this still hasn't been implemented. It might be a good idea to also check in with the development chat room before starting, especially since it's your first issue in the project.

@mark-monteiro commented on GitHub (Dec 9, 2025): @LezardSC I haven't been involved in the project in a while so I'm not 100% sure, but as far as I know this still hasn't been implemented. It might be a good idea to also check in with the [development chat room](https://jellyfin.org/contact) before starting, especially since it's your first issue in the project.

OVERLORD commented

2026-02-06 20:50:18 +03:00

@AdrianEdelen commented on GitHub (Jan 9, 2026):

I think with the recent changes with EF Core and migration behavior and overall database overhaul this maybe isn't needed anymore? One of the features being actively developed is custom database access for plugins, which should allow plugins to have their own database. In my opinion this effectively covers this issues goal.

@AdrianEdelen commented on GitHub (Jan 9, 2026): I think with the recent changes with EF Core and migration behavior and overall database overhaul this maybe isn't needed anymore? One of the features being actively developed is custom database access for plugins, which should allow plugins to have their own database. In my opinion this effectively covers this issues goal.

OVERLORD commented

2026-02-06 20:50:19 +03:00

@mark-monteiro commented on GitHub (Jan 10, 2026):

I think with the recent changes with EF Core and migration behavior and overall database overhaul this maybe isn't needed anymore? One of the features being actively developed is custom database access for plugins, which should allow plugins to have their own database. In my opinion this effectively covers this issues goal.

This issue isn't related to the database, it's about a separate migration framework for running code-based migrations on the server

@mark-monteiro commented on GitHub (Jan 10, 2026): > I think with the recent changes with EF Core and migration behavior and overall database overhaul this maybe isn't needed anymore? One of the features being actively developed is custom database access for plugins, which should allow plugins to have their own database. In my opinion this effectively covers this issues goal. This issue isn't related to the database, it's about a separate migration framework for running code-based migrations on the server

Sign in to join this conversation.

Branches Tags

master

renovate/major-skiasharp-monorepo

renovate/sharpcompress-0.x

renovate/svg.skia-5.x

renovate/ghcr.io-devcontainers-features-docker-in-docker-4.x

release-10.11.z

standards-fix

release-10.9.z

openapi-cache

release-10.10.z

explicit-load

explicit-load-v2

feature/entity-framework

only-count-folder-item

fix/ci-workflow-refactor

release-10.8.z

release-10.7.z

EraYaN-add-management-interface

release-10.6.z

release-10.5.z

release-10.4.z

release-10.3.z

release-10.2.z

release-10.1.0

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#1349