Please add withSchema back to the code. It is indeed not needed for the code to function. But it makes the code more readable for humans. :)

Done, did you mean something like this? 2ced55e

Almost. :D What I meant is that passing true and false to functions can impair readablity. You have to look at the function signature to understand what true and false mean. If you "alias" true to "withSchema" and "withoutSchema", it becomes clear to the reader what true/false means.

In the previous version of the code, I would like have a local variable in latestMigrationCmd named withoutSchema set to false. In latestSchemaCmd a local varaible named withSchema set to true. Then pass those variables to latestVersionLocal` like:

latestVersion, err = latestVersionLocal(ctx, migrationsDir, withSchema)

and

latestVersion, err = latestVersionLocal(ctx, migrationsDir, withoutSchema)

This is done, as discussed in DMs, I ended up using withSchema and !withSchema instead of withoutSchema = false

The duplication between latestMigrationCmd and latestSchemaCmd could be removed by adding a function:

// getLatestVersion returns the latest migration version from a local
// migrations directory or remote database, optionally prepending the schema
// name to which the migration is applied.
func getLatestVersion(ctx context.Context, migrationsDir string, withSchema bool) (string, error) {
	if migrationsDir != "" {
		return latestVersionLocal(ctx, migrationsDir, withSchema)
	}
	return latestVersionRemote(ctx, withSchema)
}

and using it from both latestMigrationCmd and latestSchemaCmd.

This is done.