-
-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doctrine:migrations:migrate command errors when at latest version #1011
Comments
I forgot the |
[ERROR] The version "latest" couldn't be reached, you are at version "0"
|
What changed? Some package somewhere was updated. This BC occurred. |
@9ae8sdf76 See #1015, that should make this behavior compatible with the previous 2.x version |
@BonBonSlick please avoid posting questions not related to this ticket. If you have questions please open a dedicated ticket. |
Bug Report
Summary
Since upgrading, running
bin/console doctrine:migrations:migrate -n
is being considered an error, and it is returning an error code of1
. This breaks command-line utilities that use the exit status to determine the success of migrations - e.g., CI/CD deployment pipelines.Prior to upgrading (back in the 1.x branches), running the migration tool was considered idempotent and would not produce the error it does now.
Current behavior
When running
bin/console doctrine:migrations:migrate -n
, I get the following error, and an exist state of1
:How to reproduce
Run
bin/console doctrine:migrations:migrate -n
when you are already up-to-date on migrations.Expected behavior
Running
bin/console doctrine:migrations:migrate -n
should not be considered an error, and it should return with a0
(zero) status code.The text was updated successfully, but these errors were encountered: