Skip to content

fix: don't treat an already-run migration as unrecognised#1401

Merged
dantownsend merged 2 commits into
piccolo-orm:masterfrom
pctablet505:fix-1359-migration-already-run
Jul 20, 2026
Merged

fix: don't treat an already-run migration as unrecognised#1401
dantownsend merged 2 commits into
piccolo-orm:masterfrom
pctablet505:fix-1359-migration-already-run

Conversation

@pctablet505

Copy link
Copy Markdown
Contributor

Fixes #1359

When a specific migration ID passed to piccolo migrations forwards has already been run, the command now exits successfully and reports that no migrations need to be run, instead of printing <id> is unrecognised and returning an error status.

pctablet505 and others added 2 commits July 15, 2026 18:03
When a specific migration ID is requested via the forwards command and it
has already run, Piccolo now exits successfully with no migrations to run.

Fixes piccolo-orm#1359
@dantownsend
dantownsend marked this pull request as ready for review July 20, 2026 14:22
@dantownsend

Copy link
Copy Markdown
Member

Thanks for this. I think what you did was great, but I tweaked it a tiny bit just for personal preference.

@dantownsend
dantownsend merged commit e8316f8 into piccolo-orm:master Jul 20, 2026
46 checks passed
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.

Migration is unrecognised if already ran migration id is specified and there are any not launched after it

2 participants