starred/shiori

Fork 0

mirror of https://github.com/go-shiori/shiori.git synced 2026-04-25 06:25:54 +03:00

[GH-ISSUE #584] Where did the migrate command go? #311

New issue

Closed

opened 2026-02-25 23:33:55 +03:00 by kerem · 6 comments

kerem commented

2026-02-25 23:33:55 +03:00

Owner

Originally created by @idc77 on GitHub (Feb 22, 2023).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/584

v1.5.3 to v1.5.4 no migrate command. Where is it? What changed? Where is it documented?

Originally created by @idc77 on GitHub (Feb 22, 2023). Original GitHub issue: https://github.com/go-shiori/shiori/issues/584 v1.5.3 to v1.5.4 no migrate command. Where is it? What changed? Where is it documented?

kerem

2026-02-25 23:33:55 +03:00

closed this issue
added the
tag:stale
label

kerem commented

2026-02-25 23:33:56 +03:00

Author

Owner

@idc77 commented on GitHub (Feb 22, 2023):

For the record: Error running migration: Dirty database version 2. Fix and force version.

Seriously I'm about to delete this crap from my server and browers. Every new version there's some blocker that wastes my lifetime.

@idc77 commented on GitHub (Feb 22, 2023): For the record: `Error running migration: Dirty database version 2. Fix and force version.` Seriously I'm about to delete this crap from my server and browers. Every new version there's some blocker that wastes my lifetime.

kerem commented

2026-02-25 23:33:56 +03:00

Author

Owner

@fmartingr commented on GitHub (Feb 22, 2023):

You can see the details about the removal of the migrate command in the v1.5.4 release.

Have you used a dev version before or did you migrate directly from 1.5.3 to 1.5.4? I have two services running, my main one which I maintain on the latest dev version and a "stable" one to try releases and none of them gave me problems.

You can remove the dirty flag using UPDATE schema_migrations SET dirty = 0;, but if there was some problem with the migrations before you should have it on your logs.

I'm sorry that your experience is not optimal, I'm trying to improve the codebase as much as I can, but things evolve slowly 😓

@fmartingr commented on GitHub (Feb 22, 2023): You can see the details about the removal of the migrate command in the [v1.5.4 release](https://github.com/go-shiori/shiori/releases/tag/v1.5.4). Have you used a dev version before or did you migrate directly from 1.5.3 to 1.5.4? I have two services running, my main one which I maintain on the latest dev version and a "stable" one to try releases and none of them gave me problems. You can remove the dirty flag using `UPDATE schema_migrations SET dirty = 0;`, but if there was some problem with the migrations before you should have it on your logs. I'm sorry that your experience is not optimal, I'm trying to improve the codebase as much as I can, but things evolve slowly 😓

kerem commented

2026-02-25 23:33:56 +03:00

Author

Owner

@stale[bot] commented on GitHub (Apr 4, 2023):

This issue has been automatically marked as stale because it has not had any activity for quite some time.
It will be closed if no further activity occurs.
Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 4, 2023): This issue has been automatically marked as stale because it has not had any activity for quite some time. It will be closed if no further activity occurs. Thank you for your contributions.

kerem commented

2026-02-25 23:33:56 +03:00

Author

Owner

@kron4eg commented on GitHub (Apr 10, 2023):

Seriously I'm about to delete this crap from my server and browers. Every new version there's some blocker that wastes my lifetime.

Oh wow, amazing entitlement.

@kron4eg commented on GitHub (Apr 10, 2023): > Seriously I'm about to delete this crap from my server and browers. Every new version there's some blocker that wastes my lifetime. Oh wow, amazing entitlement.

kerem commented

2026-02-25 23:33:56 +03:00

Author

Owner

@kron4eg commented on GitHub (Apr 10, 2023):

@fmartingr there is nothing to fix here, I suppose you can close the issue.

@kron4eg commented on GitHub (Apr 10, 2023): @fmartingr there is nothing to fix here, I suppose you can close the issue.

kerem commented

2026-02-25 23:33:56 +03:00

Author

Owner

@stale[bot] commented on GitHub (May 10, 2023):

This issue has been automatically marked as stale because it has not had any activity for quite some time.
It will be closed if no further activity occurs.
Thank you for your contributions.

@stale[bot] commented on GitHub (May 10, 2023): This issue has been automatically marked as stale because it has not had any activity for quite some time. It will be closed if no further activity occurs. Thank you for your contributions.