🎉 Payload 2.0 Released

[denolfe]

We're happy to announce that Payload 2.0 has been released!

The blog post with full details and video walkthroughs.

Also have a look at the release notes if you are upgrading from v1.

[hunghvu]

Congrats! Will look into migrating my company production project to v2.0!

[balmacefa]

Thank you for providing an update!

I've had issues migrating from v.1 to v.1.x in the past; payload cms updates usually stabilise around 2/3 weeks; have you considered a release candidate flow before to uncover bugs and enhance the updating guides?

[DanRibbens]

We were doing beta releases and working furiously last week upgrade templates and plugins which were public betas, we just didn't broadcast it. Now that we are situated with our monorepo we are in a much better place to iterate on releases and are talking about how we will use tags for betas or another way to automate this in the future.

Good feedback, we're going to continue to improve release management!

[alialali313]

G

[grundiss]

Hey team!
Great work, thank you :)
I have 2 questions:

1. I wonder for how long you are planning to support 1.x?
2. Is there an official 1x-to-2.0 migration guide? Like moving stuff from mongo to postgress and from Slate to Lexical?

[jacobsfletch]

We will continue to support 1.x for security fixes only, as necessary. RE: Slate->Lexical, roping in @AlessioGr here. He's been working on making this as painless as possible. For general help migrating from 1.x->2.x, you can reference our Examples Directory where most of the examples have been migrated over to 2.0 already, as well as our Templates Directory. Here's a pretty clean PR showing all the changes made to the Auth Example.

[AlessioGr]

Migration from Slate to Lexical is SUPER simple! Here's a video showcasing it:

Screenshot_2023-10-14_at_00.41.38.mp4

Simply

1. Change the field definition from Slate to Lexical (by changing the editor property)
2. Now, obviously, the lexical editor sits on top of Slate data, which it cannot read... Oh wait, it actually can! Just add the SlateToLexicalFeature() to the lexical editor, and done!

Now, if you are happy with the conversion, you can save the document (so it overrides the Slate data with the converted Lexical data) and remove the SlateToLexicalFeature (if you want. you don't have to).

If you have any custom Slate nodes added, you can simply add your own converter for those nodes as props to the SlateToLexicalFeature.

This is all very new and not documented yet - documentation will follow soon

[STR1234]

Thank you so much @AlessioGr :) Amazing stuff and thanks for the video and your effort here - so hyped to try Lexical 👍

[STR1234]

Thanks @jacobsfletch - looking forward to the migration of my projects :)

[ChristopherNowlan]

@STR1234 @AlessioGr doesn't look like Lexical works with the plugin-form-builder plugin :(

[tylerwatrich]

Very excited about this! The new lexical editor looks very promising!

[alialali313]

H

[tiagomarin]

How could I start the project already on 2.0? Or I always need to install 1.0 and then upgrade it manually?
It seems that npx create-payload-app@latest creates a 1.0 project.