What's up everyone? Welcome to Next In Dev. In this episode, I'll discuss exciting new updates from Payload and Railway, and more. I had a good time trying to get the new MCP server plugin working in Payload CMS.
If you wanna see the live stream, you can find it on YouTube. I'm looking forward to diving back into it and more soon.
The Payload CMS team released version three point sixty-one point one, which has some bug fixes, and version three point sixty-two. Version three point sixty-one point one contained bug fixes and documentation updates.
The team released it as a quick follow-up to three point sixty. The primary bug fix appears to be that the UI now asks before closing a document drawer that's been edited.
Version three point sixty-two has some exciting features. Here they are in quick succession. You can now edit the access controls for the queue and cancel operations in job scheduling.
Each date field can now have their own time zone settings. That means different date fields can support their own list of time zones and default values.
With this new change, you can enforce one time zone by adding one time zone in the supported time zones array and setting it as the default. You can set where you want toasts to be positioned on the screen.
You can put the toast in any of the corners or top or bottom center. The team has added KV storage adapters. The Payload team is setting the stage for real-time and new caching processes.
You can enable it by setting the new KV property and initializing a database in memory or Redis adapter. I'm excited for the new features this will unlock. Schema by Figma was this week.
They introduced some new design changes, things like extended collections, new slots, and a way to audit designs. The team also spoke a lot about updates coming to variables.
The Figma team also announced that they're expanding the MCP server to their starter plan this week. This isn't a new feature, but it's rolling out to a broader audience. Also on the code side of Figma is CodeConnect.
This improves the connection between source files and example code. The last things worth calling out are the ability to use NPM packages and the Figma design library with Figma Make.
Next.js sixteen point zero point one is the newest version released by the Next.js team. This version fixes type issues in the Next Markdown package.
It also upgrades the React version, updates documentation, and adjusts Turbopack. Cloudflare released a proposal for a registry of approved bots and agents.
This is currently in theory, and there's not anything concrete yet. It's a worthy goal, though. OpenAI released a preview of their safety classification tasks.
OpenAI continues to face scrutiny over their handling of sensitive conversations, so I guess this is a step in the right direction.
Primarily, it seems like developers will be using this model when they use ChatGPT as their chat feature on their sites. This model allows the developers to set the safeguards themselves.
Microsoft and OpenAI released a PR statement talking about Microsoft's new investment into OpenAI. There are some exclusivity clauses included in the deal, so it's not all free money for OpenAI.
It is wild how much money Microsoft has poured into OpenAI. Cursor released a few new features worth calling out. The first is the ability to use speech-to-text with Cursor with a new built-in tool.
You don't need another platform to speak to your favorite AI IDE anymore. Also, you can use plan mode with one model and build with another. It's nice to be able to do both at the same time.
And oh man, I'm excited for this Railway news. How has no one done this yet? They've released what they're calling Magic Config in beta.
This scans your code and adds all your environment variables automatically, and it stays in sync with your code. You still have to enter in your variable values of course, but I'm going to have to try this out soon.
I mentioned last week that secure database access was in beta. Well, it's already generally available. At React's conference this year, Meta announced it's donating React and React Native to the Linux Foundation.
The Linux Foundation will create a new foundation called the React Foundation. This foundation will take over governance, core infrastructure, and events.
The founding members of the foundation will come from Amazon, Meta, Vercel, and more. It's hard to see that corporate influence will be neutral. Vercel especially has high stakes in React going in a certain direction.
Thanks for listening. I'll see you next time.