unexpected version reported when running 'goose up' in the no change case

[jonseymour]

description

Currently, when goose runs up in the fully applied state, it reports 0 as the current version rather than the actual current version. This is not expected.

actual output

platform/main@local >goose down
2023/06/10 13:32:48 OK   00297_initial_warehouse_version.sql (10.3ms)
platform/main@local >goose up
2023/06/10 13:32:50 OK   00297_initial_warehouse_version.sql (13.48ms)
2023/06/10 13:32:50 goose: no migrations to run. current version: 297
platform/main@local >goose version
2023/06/10 13:33:04 goose: version 297
platform/main@local >goose up
2023/06/10 13:33:06 goose: no migrations to run. current version: 0

expected output

platform/main@local >goose down
2023/06/10 13:32:48 OK   00297_initial_warehouse_version.sql (10.3ms)
platform/main@local >goose up
2023/06/10 13:32:50 OK   00297_initial_warehouse_version.sql (13.48ms)
2023/06/10 13:32:50 goose: no migrations to run. current version: 297
platform/main@local >goose version
2023/06/10 13:33:04 goose: version 297
platform/main@local >goose up
2023/06/10 13:33:06 goose: no migrations to run. current version: 297

goose version

goose version:v3.11.2-1-upowr-g3d345c4

e.g. (our local build of the current master version of goose)

[mfridman]

Thanks for the report, fixed in #533. Just needed to remove a check on that log line, doesn't affect migrations themselves.