🎉 Announcing Baserow 2.1: Expert formula mode, infrastructure upgrades, and improved maintainability!

[olgatrykush]

We’re excited to share our latest release!

Baserow 2.1 is a maintenance-focused update that improves performance, security, and long-term stability, while also introducing expert formula mode.

Here’s what’s new:

→ Expert formula mode: Combine data, functions, and operators across Applications, Automations, and AI fields
→ Infrastructure upgrades: Migration to Nuxt 3 and Django backend upgrade
→ Smaller & faster Docker images: Improved production efficiency for self-hosted deployments
→ PostgreSQL update: PostgreSQL 13 is no longer supported (upgrade to 14+)
→ New Ukrainian translation thanks to @dospolov

See what’s new in Baserow 2.1

We’re continuously improving Baserow based on your feedback. Try the new release and let us know what you think!

[walden]

Is there a way to downgrade the Docker AIO back to version 2.0.1? The 2.1 update broke my application and I don’t have time to research why at the moment.

When clicking a button that does a bunch of actions, I get an error when it gets to the step “Add a row” with one of the fields empty (it’s an optional field).

Invalid form

The “Create a row” action failed: One or more fields contain invalid values.

Value error for field “\[optional field here\]“: None is not a valid number

[olgatrykush]

Hello @walden

Yes, downgrading is possible. However, we recommend rolling back to version 2.0.6 rather than 2.0.1.

To do this, you can follow the same process as when upgrading:

1. Stop your Docker all-in-one container.
2. Change the image version to 2.0.6.
3. Start the container again.

[walden]

Thank you! It wasn’t working but after looking at the logs I saw Redis was the problem. I renamed the file inside the Redis folder so it would be recreated, and all is well now. Running 2.0.6.

[Edouard]

Hello, we are facing the same problem as walden since the release of 2.1 (Saas mode).

I ve created a topic about it :

Error on send an http request event since 2.1

Hello everyone, I am facing an issue with a Post HTTP request triggered at the submission of a form. The event was working fine before the 2.1 release. It was just sending a JSON that looks like this : [image] The problem i face is that some of the field can be empty when the form is submitted. Before it wasn’t an issue but now it gives the following error : [image] So i thought ok no problem i will switch to expert mode to work around it but i am actually unable to switch to expert mode…

[olgatrykush]

Hey @Edouard, thanks for pointing this out! As discussed in the topic, a fix for this bug is on the way.

[walden]

My problem is resolved with subsequent updates (2.1.3 at the time of this comment). Thanks!