Skip to content

Conversation

Flogex
Copy link
Contributor

@Flogex Flogex commented Feb 25, 2025

Updates version_map.json to include a storage and serialization version for the upcoming v1.2.1 release

@Flogex Flogex changed the title Add serialization and storage version for v1.2.1 Add storage and serialization version for v1.2.1 Feb 25, 2025
@Mytherin
Copy link
Collaborator

Thanks! LGTM - could you just have a look at the failing tests?

@duckdb-draftbot duckdb-draftbot marked this pull request as draft February 25, 2025 22:48
@Flogex Flogex marked this pull request as ready for review February 26, 2025 07:12
@Flogex
Copy link
Contributor Author

Flogex commented Feb 26, 2025

I have updated the tests to expect the new name "v1.2.0 - v1.2.1" for the storage version tag.

@carlopi
Copy link
Contributor

carlopi commented Feb 26, 2025

Not for this PR, but connected: do we might want to change the results OR adapt the tests to filter only the start instead of the range.

Maybe:

{storage_version=v1.0.0+}
{storage_version=v1.2.0+}

(either directly as result or filtering results to the first X chars)
could make more sense to avoid having to adapt tests on new versions?

@Mytherin Mytherin merged commit 9f42783 into duckdb:v1.2-histrionicus Feb 26, 2025
50 checks passed
@Mytherin
Copy link
Collaborator

Thanks!

Not for this PR, but connected: do we might want to change the results OR adapt the tests to filter only the start instead of the range.

Yes that makes sense

krlmlr added a commit to duckdb/duckdb-r that referenced this pull request Mar 7, 2025
Add storage and serialization version for v1.2.1 (duckdb/duckdb#16403)
Mytherin added a commit that referenced this pull request Mar 24, 2025
…h release (#16799)

This is equivalent to #16403,
problem is still open of handling this in a more general way to avoid
PRs like this one.

I think for `v1.2.2` is fine do to this manually, on `main` it would be
cool to handle this so that only on introducing a different version this
will require changes, but adding a patch release should touch
src/storage/version_map.json but not the tests.
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.

3 participants