🚀 2.6.0b1 checklist ✅

[sydney-runkle]

Collection of issues to complete + PRs to finish before the upcoming minor release:

• Explicitly raise an error if field names clashes with types #8243
• feat: enable json schema creation with type ByteSize #8537
• Override dataclass_transform behavior for RootModel #8163
• Add eval_type_backport to handle union operator and builtin generic subscripting in older Pythons #8209 - highly desirable (added by @samuelcolvin, cc @alexmojaki)
• Add support for dataclass fields init #8552, which depends on Add support for dataclass fields init pydantic-core#1163
• fix for #8512 #8567
• Roll over issues from 2.6.0 milestone to 2.7.0 if they have not yet been completed

Optional:

• dataclass serialization speedups pydantic-core#1162 would be nice to have (@samuelcolvin)

As a prerequisite, we'll do a V1 patch release, for which we'd like to finish these:

• Ubuntu fixes for V1 #8540
• Fix cached_property handling in dataclasses when copied #8407

[hramezani]

If we want to do a V1 patch release, I suggest doing it before V2 2.6 release then we can include the latest V1 in pydantic.v1 namespace.

[sydney-runkle]

@hramezani,

Good call. I've updated the issue description:

As a prerequisite, we'll do a V1 patch release, for which we'd like to finish these:

[sydney-runkle]

@Viicos @romulocollopy,

I think there's some more work we need to do in order to get #6814 across the line, which is currently blocking ##6563.

Let's make these a priority for 2.7.0, which shouldn't come out too long after 2.6.0 🚀.

I've removed these from the list above.

[Viicos]

#6563 might not be blocked by #6814 (depending of the usage of __name__), but it requires some review still so if you want to have 2.6 landing soon then yes it might be worth going for 2.7!

[sydney-runkle]

@Viicos,

Let's stick with 2.7, but we focus on it soon after the release of 2.6 :). Looking forward to reviewing more thoroughly soon! 🚀

[sydney-runkle]

Everything here is done :). Marking this as closed, and will work on releasing 2.6 here shortly.

Thanks to everyone who has worked hard on this!

[einarwar]

Sorry for commenting on a closed issue. Do you have any expected release date for 2.6.0 @sydney-runkle? Some very anticipated fixes there for our project :)

[sydney-runkle]

@einarwar,

No worries at all! We're releasing it today :). Keep an eye out for a tweet soon!