The list of changes for this release is long. It ranges from improved password validation to Heroku templates to bug fixes. View the full list at the bottom of this post for a complete overview. We also worked on three bigger features. Never lose track of when a row is created or modified with the created on and last modified field types. Have you ever needed a place to discuss a row in more detail or do you simply want explain what you have changed? You can do that with our new premium row comments feature which will be available in the upcoming premium version of Baserow.
It is now possible to keep track of when a row was last changed and when it was initially created by two new field types. The “Last Modified” field shows the date when that row was last updated. The “Created On” field will show the date when the row was initially created. You can optionally include the time in both. The fields are read only and can’t be edited directly. All the expected date filters are also available for these field.
In the premium version of Baserow (available soon!) you and others in your group can now leave comments on rows. Comments are sent instantly to everyone else in your group, so you can chat in real-time using them. To add a row comment you first click the expand row button which appears on the left hand side of the row when hovering over or selecting a row. Then the row comments sidebar will be visible where you can see existing comments and add your own.
We received a lot requests regarding filters related to a link to table field. We have now introduced two new filters to check if a link to table field `has` or `has not` a relationship. Simple create the filter, choose a related row and you will only see rows that have a relationship with the chosen row.
It is now even easier to self host Baserow because we now have a Heroku template. Install by clicking on the one click deploy to Heroku button. More information and the button can be found in our documentation.
All the changes of version 1.5 listed.
Warning: From version 0.8.0 to 1.4.1 of Baserow the docker-compose.yml included in the root of this repository has exposed an unsecured redis instance by default on the ip:port 0.0.0.0:6379. If you have been running a server which is accessible via the internet using this docker-compose.yml then it is possible this redis server has been exposed to the internet depending on your operating system, networking setup and firewall settings. Please update to the latest version of Baserow, 1.4.2 which no longer exposes the redis, db and mjml containers. Additionally, 1.4.2 only exposes the backend, web-frontend and media containers on localhost and not on 0.0.0.0. If you were previously relying on docker-compose.yml publicly exposing Baserow then please follow the make Baserow publicly accessible section in the docker how to guide.
Today we are releasing Baserow 1.14 with a new security feature — audit log, and big updates to Baserow RBAC that allow assigning roles to users or teams on individual databases and tables for even more granular permission control.
Want to write a post in collaboration with us?How to contribute?