Migration error message reports incorrect version number

[szarnyasg]

What happens?

Trying to attach to a remote v0.3 DuckLake with AUTOMATIC_MIGRATION fails and prints an incorrect error message.

To Reproduce

Run the nightly DuckDB with ducklake:

ATTACH 'ducklake:https://datasets.ldbcouncil.org/snb-interactive-v1-ducklake/sf1.ducklake' (AUTOMATIC_MIGRATION);

Invalid Input Error:
Failed to migrate DuckLake from v0.2 to v0.3:Cannot execute statement of type "CREATE" on database "__ducklake_metadata_sf1" which is attached in read-only mode!

As far as I understand, the failure is expected but the error message is misleading at the moment.
Here's the metadata of the DuckLake from DuckDB v1.4.4:

FROM __ducklake_metadata_sf1.ducklake_metadata;
┌────────────┬──────────────────────────────────────────────────────────────────┬─────────┬──────────┐
│    key     │                              value                               │  scope  │ scope_id │
│  varchar   │                             varchar                              │ varchar │  int64   │
├────────────┼──────────────────────────────────────────────────────────────────┼─────────┼──────────┤
│ version    │ 0.3                                                              │ NULL    │     NULL │
│ created_by │ DuckDB 6ddac802ff                                                │ NULL    │     NULL │
│ data_path  │ https://datasets.ldbcouncil.org/snb-interactive-v1-ducklake/sf1/ │ NULL    │     NULL │
│ encrypted  │ false                                                            │ NULL    │     NULL │
└────────────┴──────────────────────────────────────────────────────────────────┴─────────┴──────────┘

OS:

any

DuckDB Version:

nightly

DuckLake Version:

nightly

DuckDB Client:

CLI

Hardware:

No response

Full Name:

Gabor Szarnyas

Affiliation:

DuckDB Labs

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a nightly build

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include all code required to reproduce the issue?

• Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

• Yes, I have