From 252f15275e28ca5f5a2dff4d063610ad9daf9c36 Mon Sep 17 00:00:00 2001
From: Bram Wiepjes <bramw@protonmail.com>
Date: Thu, 14 Mar 2024 10:11:12 +0000
Subject: [PATCH] Prepared for 1.23.2 release
---
README.md | 4 +-
backend/docker/docker-entrypoint.sh | 2 +-
backend/setup.py | 2 +-
backend/src/baserow/config/settings/base.py | 2 +-
backend/src/baserow/version.py | 2 +-
changelog.md | 6 +++
.../bug/fix_thread_safely_get_model.json | 7 ++++
changelog/releases.json | 4 ++
deploy/all-in-one/README.md | 32 ++++++++--------
deploy/all-in-one/supervisor/start.sh | 2 +-
deploy/cloudron/CloudronManifest.json | 2 +-
deploy/cloudron/Dockerfile | 2 +-
deploy/render/Dockerfile | 2 +-
docker-compose.all-in-one.yml | 2 +-
docker-compose.no-caddy.yml | 10 ++---
docker-compose.yml | 10 ++---
docs/installation/install-behind-apache.md | 12 +++---
docs/installation/install-behind-nginx.md | 12 +++---
docs/installation/install-on-aws.md | 28 +++++++-------
docs/installation/install-on-cloudron.md | 4 +-
docs/installation/install-on-digital-ocean.md | 4 +-
docs/installation/install-on-ubuntu.md | 4 +-
.../install-using-standalone-images.md | 12 +++---
.../install-with-docker-compose.md | 2 +-
docs/installation/install-with-docker.md | 38 +++++++++----------
docs/installation/install-with-k8s.md | 12 +++---
docs/installation/install-with-traefik.md | 2 +-
docs/installation/supported.md | 2 +-
docs/plugins/creation.md | 2 +-
docs/plugins/installation.md | 26 ++++++-------
heroku.Dockerfile | 2 +-
.../Dockerfile | 2 +-
.../backend-dev.Dockerfile | 4 +-
.../backend.Dockerfile | 2 +-
.../dev.Dockerfile | 4 +-
.../baserow_plugin_info.json | 2 +-
.../web-frontend-dev.Dockerfile | 4 +-
.../web-frontend.Dockerfile | 2 +-
web-frontend/docker/docker-entrypoint.sh | 2 +-
web-frontend/package.json | 2 +-
40 files changed, 147 insertions(+), 130 deletions(-)
create mode 100644 changelog/entries/1.23.2/bug/fix_thread_safely_get_model.json
diff --git a/README.md b/README.md
index 8bdea36c9..27b7b1fde 100644
--- a/README.md
+++ b/README.md
@@ -17,7 +17,7 @@ tool gives you the powers of a developer without leaving your browser.
[](https://heroku.com/deploy?template=https://github.com/bram2w/baserow/tree/master)
```bash
-docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.23.1
+docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.23.2
```
@@ -89,7 +89,7 @@ Created by Baserow B.V. - bram@baserow.io.
Distributes under the MIT license. See `LICENSE` for more information.
-Version: 1.23.1
+Version: 1.23.2
The official repository can be found at https://gitlab.com/baserow/baserow.
diff --git a/backend/docker/docker-entrypoint.sh b/backend/docker/docker-entrypoint.sh
index 7a855320e..e694233f7 100755
--- a/backend/docker/docker-entrypoint.sh
+++ b/backend/docker/docker-entrypoint.sh
@@ -6,7 +6,7 @@ set -euo pipefail
# ENVIRONMENT VARIABLES USED DIRECTLY BY THIS ENTRYPOINT
# ======================================================
-export BASEROW_VERSION="1.23.1"
+export BASEROW_VERSION="1.23.2"
# Used by docker-entrypoint.sh to start the dev server
# If not configured you'll receive this: CommandError: "0.0.0.0:" is not a valid port number or address:port pair.
diff --git a/backend/setup.py b/backend/setup.py
index c85b50bdb..e85fe45c2 100644
--- a/backend/setup.py
+++ b/backend/setup.py
@@ -5,7 +5,7 @@ from setuptools import find_packages, setup
PROJECT_DIR = os.path.dirname(__file__)
REQUIREMENTS_DIR = os.path.join(PROJECT_DIR, "requirements")
-VERSION = "1.23.1"
+VERSION = "1.23.2"
def get_requirements(env):
diff --git a/backend/src/baserow/config/settings/base.py b/backend/src/baserow/config/settings/base.py
index 1a4b83cc9..62d86acf2 100644
--- a/backend/src/baserow/config/settings/base.py
+++ b/backend/src/baserow/config/settings/base.py
@@ -484,7 +484,7 @@ SPECTACULAR_SETTINGS = {
"name": "MIT",
"url": "https://gitlab.com/baserow/baserow/-/blob/master/LICENSE",
},
- "VERSION": "1.23.1",
+ "VERSION": "1.23.2",
"SERVE_INCLUDE_SCHEMA": False,
"TAGS": [
{"name": "Settings"},
diff --git a/backend/src/baserow/version.py b/backend/src/baserow/version.py
index 97a12b91e..d63c70276 100644
--- a/backend/src/baserow/version.py
+++ b/backend/src/baserow/version.py
@@ -1 +1 @@
-VERSION = "1.23.1"
+VERSION = "1.23.2"
diff --git a/changelog.md b/changelog.md
index e697a4eb2..9c4aa1711 100644
--- a/changelog.md
+++ b/changelog.md
@@ -1,5 +1,11 @@
# Changelog
+## Released 1.23.2
+
+### Bug fixes
+* Fix thread safety bug of the table get_model method. [#2421](https://gitlab.com/baserow/baserow/-/issues/2421)
+
+
## Released 1.23.1
### New features
diff --git a/changelog/entries/1.23.2/bug/fix_thread_safely_get_model.json b/changelog/entries/1.23.2/bug/fix_thread_safely_get_model.json
new file mode 100644
index 000000000..2fb10ebbe
--- /dev/null
+++ b/changelog/entries/1.23.2/bug/fix_thread_safely_get_model.json
@@ -0,0 +1,7 @@
+{
+ "type": "bug",
+ "message": "Fix thread safety bug of the table get_model method.",
+ "issue_number": 2421,
+ "bullet_points": [],
+ "created_at": "2024-03-14"
+}
diff --git a/changelog/releases.json b/changelog/releases.json
index b1bdbd06f..2aa919049 100644
--- a/changelog/releases.json
+++ b/changelog/releases.json
@@ -1,5 +1,9 @@
{
"releases": [
+ {
+ "name": "1.23.2",
+ "created_at": "2024-03-14"
+ },
{
"name": "1.23.1",
"created_at": "2024-03-13"
diff --git a/deploy/all-in-one/README.md b/deploy/all-in-one/README.md
index eabe5c488..e76759404 100644
--- a/deploy/all-in-one/README.md
+++ b/deploy/all-in-one/README.md
@@ -15,7 +15,7 @@ tool gives you the powers of a developer without leaving your browser.
[Vue.js](https://vuejs.org/) and [PostgreSQL](https://www.postgresql.org/).
```bash
-docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.23.1
+docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.23.2
```
## Quick Reference
@@ -50,7 +50,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
* Change `BASEROW_PUBLIC_URL` to `https://YOUR_DOMAIN` or `http://YOUR_IP` to enable
@@ -72,7 +72,7 @@ docker run \
## Image Feature Overview
-The `baserow/baserow:1.23.1` image by default runs all of Baserow's various services in a
+The `baserow/baserow:1.23.2` image by default runs all of Baserow's various services in a
single container for ease of use. A quick summary of its features are:
* Runs a Postgres database and Redis server by default internally and stores all data in
@@ -115,7 +115,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### Behind a reverse proxy already handling ssl
@@ -128,7 +128,7 @@ docker run \
-v baserow_data:/baserow/data \
-p 80:80 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### On a nonstandard HTTP port
@@ -141,7 +141,7 @@ docker run \
-v baserow_data:/baserow/data \
-p 3001:80 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### With an external PostgresSQL server
@@ -160,7 +160,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### With an external Redis server
@@ -179,7 +179,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### With an external email server
@@ -199,7 +199,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### Start just the embedded database
@@ -212,7 +212,7 @@ docker run -it \
--name baserow \
-p 5432:5432 \
-v baserow_data:/baserow/data \
- baserow/baserow:1.23.1 \
+ baserow/baserow:1.23.2 \
start-only-db
# Now get the password from
docker exec -it baserow cat /baserow/data/.pgpass
@@ -230,7 +230,7 @@ docker run -it \
--rm \
--name baserow \
-v baserow_data:/baserow/data \
- baserow/baserow:1.23.1 \
+ baserow/baserow:1.23.2 \
backend-cmd-with-db manage dbshell
```
@@ -299,16 +299,16 @@ the command below.
```bash
# First read the help message for this command
-docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.23.1 \
+docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.23.2 \
backend-cmd-with-db backup
# By default backs up to the backups folder in the baserow_data volume.
-docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.23.1 \
+docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.23.2 \
backend-cmd-with-db backup -f /baserow/data/backups/backup.tar.gz
# Or backup to a file on your host instead run something like:
docker run -it --rm -v baserow_data:/baserow/data -v $PWD:/baserow/host \
- baserow/baserow:1.23.1 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
+ baserow/baserow:1.23.2 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
```
### Restore only Baserow's Postgres Database
@@ -377,7 +377,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
Or you can just store it directly in the volume at `baserow_data/env` meaning it will
@@ -386,7 +386,7 @@ be loaded whenever you mount in this data volume.
### Building your own image from Baserow
```dockerfile
-FROM baserow/baserow:1.23.1
+FROM baserow/baserow:1.23.2
# Any .sh files found in /baserow/supervisor/env/ will be sourced and loaded at startup
# useful for storing your own environment variable overrides.
diff --git a/deploy/all-in-one/supervisor/start.sh b/deploy/all-in-one/supervisor/start.sh
index 056e9ca8b..eb3cedb43 100755
--- a/deploy/all-in-one/supervisor/start.sh
+++ b/deploy/all-in-one/supervisor/start.sh
@@ -14,7 +14,7 @@ cat << EOF
██████╔╝██║ ██║███████║███████╗██║ ██║╚██████╔╝╚███╔███╔╝
╚═════╝ ╚═╝ ╚═╝╚══════╝╚══════╝╚═╝ ╚═╝ ╚═════╝ ╚══╝╚══╝
-Version 1.23.1
+Version 1.23.2
=========================================================================================
EOF
diff --git a/deploy/cloudron/CloudronManifest.json b/deploy/cloudron/CloudronManifest.json
index 2e66a6f1c..5a862fd0e 100644
--- a/deploy/cloudron/CloudronManifest.json
+++ b/deploy/cloudron/CloudronManifest.json
@@ -8,7 +8,7 @@
"contactEmail": "bram@baserow.io",
"icon": "file://logo.png",
"tags": ["no-code", "nocode", "database", "data", "collaborate", "airtable"],
- "version": "1.23.1",
+ "version": "1.23.2",
"healthCheckPath": "/api/_health/",
"httpPort": 80,
"addons": {
diff --git a/deploy/cloudron/Dockerfile b/deploy/cloudron/Dockerfile
index d78a0c825..204880472 100644
--- a/deploy/cloudron/Dockerfile
+++ b/deploy/cloudron/Dockerfile
@@ -1,4 +1,4 @@
-ARG FROM_IMAGE=baserow/baserow:1.23.1
+ARG FROM_IMAGE=baserow/baserow:1.23.2
# This is pinned as version pinning is done by the CI setting FROM_IMAGE.
# hadolint ignore=DL3006
FROM $FROM_IMAGE as image_base
diff --git a/deploy/render/Dockerfile b/deploy/render/Dockerfile
index 9ab90ffb9..8d9b0baf7 100644
--- a/deploy/render/Dockerfile
+++ b/deploy/render/Dockerfile
@@ -1,4 +1,4 @@
-ARG FROM_IMAGE=baserow/baserow:1.23.1
+ARG FROM_IMAGE=baserow/baserow:1.23.2
# This is pinned as version pinning is done by the CI setting FROM_IMAGE.
# hadolint ignore=DL3006
FROM $FROM_IMAGE as image_base
diff --git a/docker-compose.all-in-one.yml b/docker-compose.all-in-one.yml
index 489f6d3ef..779e1f600 100644
--- a/docker-compose.all-in-one.yml
+++ b/docker-compose.all-in-one.yml
@@ -4,7 +4,7 @@ version: "3.4"
services:
baserow:
container_name: baserow
- image: baserow/baserow:1.23.1
+ image: baserow/baserow:1.23.2
environment:
BASEROW_PUBLIC_URL: 'http://localhost'
ports:
diff --git a/docker-compose.no-caddy.yml b/docker-compose.no-caddy.yml
index 31c71eaab..19efd16f6 100644
--- a/docker-compose.no-caddy.yml
+++ b/docker-compose.no-caddy.yml
@@ -166,7 +166,7 @@ x-backend-variables: &backend-variables
services:
backend:
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
restart: unless-stopped
ports:
- "${HOST_PUBLISH_IP:-127.0.0.1}:8000:8000"
@@ -181,7 +181,7 @@ services:
local:
web-frontend:
- image: baserow/web-frontend:1.23.1
+ image: baserow/web-frontend:1.23.2
restart: unless-stopped
ports:
- "${HOST_PUBLISH_IP:-127.0.0.1}:3000:3000"
@@ -215,7 +215,7 @@ services:
local:
celery:
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
restart: unless-stopped
environment:
<<: *backend-variables
@@ -232,7 +232,7 @@ services:
local:
celery-export-worker:
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
restart: unless-stopped
command: celery-exportworker
environment:
@@ -249,7 +249,7 @@ services:
local:
celery-beat-worker:
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
restart: unless-stopped
command: celery-beat
environment:
diff --git a/docker-compose.yml b/docker-compose.yml
index bdf45a017..e0bd9a57b 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -190,7 +190,7 @@ services:
local:
backend:
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
restart: unless-stopped
environment:
<<: *backend-variables
@@ -203,7 +203,7 @@ services:
local:
web-frontend:
- image: baserow/web-frontend:1.23.1
+ image: baserow/web-frontend:1.23.2
restart: unless-stopped
environment:
BASEROW_PUBLIC_URL: ${BASEROW_PUBLIC_URL-http://localhost}
@@ -238,7 +238,7 @@ services:
local:
celery:
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
restart: unless-stopped
environment:
<<: *backend-variables
@@ -255,7 +255,7 @@ services:
local:
celery-export-worker:
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
restart: unless-stopped
command: celery-exportworker
environment:
@@ -272,7 +272,7 @@ services:
local:
celery-beat-worker:
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
restart: unless-stopped
command: celery-beat
environment:
diff --git a/docs/installation/install-behind-apache.md b/docs/installation/install-behind-apache.md
index 0fef9c21f..72864c6ae 100644
--- a/docs/installation/install-behind-apache.md
+++ b/docs/installation/install-behind-apache.md
@@ -3,7 +3,7 @@
If you have an [Apache server](https://www.apache.com/) this guide will explain how to
configure it to pass requests through to Baserow.
-We strongly recommend you use our `baserow/baserow:1.23.1` image or the example
+We strongly recommend you use our `baserow/baserow:1.23.2` image or the example
`docker-compose.yml` files (excluding the `.no-caddy.yml` variant) provided in
our [git repository](https://gitlab.com/baserow/baserow/-/tree/master/deploy/apache/).
@@ -18,8 +18,8 @@ simplifies your life by:
> If you do not want to use our embedded Caddy service behind your Apache then
> make sure you are using one of the two following deployment methods:
>
-> * Your own container setup with our single service `baserow/backend:1.23.1`
- and `baserow/web-frontend:1.23.1` images.
+> * Your own container setup with our single service `baserow/backend:1.23.2`
+ and `baserow/web-frontend:1.23.2` images.
> * Or our `docker-compose.no-caddy.yml` example file in our [git repository](https://gitlab.com/baserow/baserow/-/tree/master/deploy/apache/).
>
> Then you should use **Option 2: Without our embedded Caddy** section instead.
@@ -32,7 +32,7 @@ simplifies your life by:
Follow this option if you are using:
-* The all-in-one Baserow image `baserow/baserow:1.23.1`
+* The all-in-one Baserow image `baserow/baserow:1.23.2`
* Any of the example compose files found in the root of our git
repository `docker-compose.yml`/`docker-compose.local-build.yml`
/`docker-compose.all-in-one.yml`
@@ -116,7 +116,7 @@ You should now be able to access Baserow on you configured subdomain.
Follow this option if you are using:
-* Our standalone `baserow/backend:1.23.1` and `baserow/web-frontend:1.23.1` images with
+* Our standalone `baserow/backend:1.23.2` and `baserow/web-frontend:1.23.2` images with
your own container orchestrator.
* Or the `docker-compose.no-caddy.yml` example docker compose file in the root of our
git repository.
@@ -148,7 +148,7 @@ sudo systemctl restart apache2
You need to ensure user uploaded files are accessible in a folder for Apache to serve. In
the rest of the guide we will use the example `/var/web` folder for this purpose.
-If you are using the `baserow/backend:1.23.1` image then you can do this by adding
+If you are using the `baserow/backend:1.23.2` image then you can do this by adding
`-v /var/web:/baserow/data/media` to your normal `docker run` command used to launch the
Baserow backend.
diff --git a/docs/installation/install-behind-nginx.md b/docs/installation/install-behind-nginx.md
index 04ebf3183..ba7731888 100644
--- a/docs/installation/install-behind-nginx.md
+++ b/docs/installation/install-behind-nginx.md
@@ -3,7 +3,7 @@
If you have an [Nginx server](https://www.nginx.com/) this guide will explain how to
configure it to pass requests through to Baserow.
-We strongly recommend you use our `baserow/baserow:1.23.1` image or the example
+We strongly recommend you use our `baserow/baserow:1.23.2` image or the example
`docker-compose.yml` files (excluding the `.no-caddy.yml` variant) provided in
our [git repository](https://gitlab.com/baserow/baserow/-/tree/master/deploy/nginx/).
@@ -18,8 +18,8 @@ simplifies your life by:
> If you do not want to use our embedded Caddy service behind your Nginx then
> make sure you are using one of the two following deployment methods:
>
-> * Your own container setup with our single service `baserow/backend:1.23.1`
- and `baserow/web-frontend:1.23.1` images.
+> * Your own container setup with our single service `baserow/backend:1.23.2`
+ and `baserow/web-frontend:1.23.2` images.
> * Or our `docker-compose.no-caddy.yml` example file in our [git repository](https://gitlab.com/baserow/baserow/-/tree/master/deploy/nginx/).
>
> Then you should use **Option 2: Without our embedded Caddy** section instead.
@@ -32,7 +32,7 @@ simplifies your life by:
Follow this option if you are using:
-* The all-in-one Baserow image `baserow/baserow:1.23.1`
+* The all-in-one Baserow image `baserow/baserow:1.23.2`
* Any of the example compose files found in the root of our git
repository `docker-compose.yml`/`docker-compose.local-build.yml`
/`docker-compose.all-in-one.yml`
@@ -108,7 +108,7 @@ You should now be able to access Baserow on you configured subdomain.
Follow this option if you are using:
-* Our standalone `baserow/backend:1.23.1` and `baserow/web-frontend:1.23.1` images with
+* Our standalone `baserow/backend:1.23.2` and `baserow/web-frontend:1.23.2` images with
your own container orchestrator.
* Or the `docker-compose.no-caddy.yml` example docker compose file in the root of our
git repository.
@@ -127,7 +127,7 @@ but you might have to run different commands.
You need to ensure user uploaded files are accessible in a folder for Nginx to serve. In
the rest of the guide we will use the example `/var/web` folder for this purpose.
-If you are using the `baserow/backend:1.23.1` image then you can do this by adding
+If you are using the `baserow/backend:1.23.2` image then you can do this by adding
`-v /var/web:/baserow/data/media` to your normal `docker run` command used to launch the
Baserow backend.
diff --git a/docs/installation/install-on-aws.md b/docs/installation/install-on-aws.md
index 3d3665a33..a9d40554d 100644
--- a/docs/installation/install-on-aws.md
+++ b/docs/installation/install-on-aws.md
@@ -49,7 +49,7 @@ overview this is what any AWS deployment of Baserow will need:
## Option 1) Deploying the all-in-one image to Fargate/ECS
-The `baserow/baserow:1.23.1` image runs all of Baserow’s various services inside the
+The `baserow/baserow:1.23.2` image runs all of Baserow’s various services inside the
container for ease of use.
This image is designed for single server deployments or simple deployments to
@@ -67,7 +67,7 @@ Run.
* You don't need to worry about configuring and linking together the different
services that make up a Baserow deployment.
* Configuring load balancers is easier as you can just directly route through all
- requests to any horizontally scaled container running `baserow/baserow:1.23.1`.
+ requests to any horizontally scaled container running `baserow/baserow:1.23.2`.
#### Cons
@@ -75,7 +75,7 @@ Run.
* Potentially higher resource usage overall as each of the all-in-one containers will
come with its internal services, so you have less granular control over scaling
specific services.
- * For example if you deploy 10 `baserow/baserow:1.23.1` containers horizontally you
+ * For example if you deploy 10 `baserow/baserow:1.23.2` containers horizontally you
by default end up with:
* 10 web-frontend services
* 10 backend services
@@ -188,18 +188,18 @@ Generally, the Redis server is not the bottleneck in Baserow deployments as they
Now create a target group on port 80 and ALB ready to route traffic to the Baserow
containers.
-When setting up the health check for the ALB the `baserow/baserow:1.23.1` container
+When setting up the health check for the ALB the `baserow/baserow:1.23.2` container
,which you'll be deploying next, choose port `80` and health check
URL `/api/_health/`. We recommend a long grace period of 900 seconds to account for
first-time migrations being run on the first container's startup.
#### 5) Launching Baserow on ECS/Fargate
-Now we are ready to spin up our `baserow/baserow:1.23.1` containers. See below for a
+Now we are ready to spin up our `baserow/baserow:1.23.2` containers. See below for a
full task definition and environment variables. We recommend launching the containers
with 2vCPUs and 4 GB of RAM each to start with. In short, you will want to:
-1. Select the `baserow/baserow:1.23.1` image.
+1. Select the `baserow/baserow:1.23.2` image.
2. Add a port mapping of `80` on TCP as this is where this images HTTP server is
listening by default.
3. Mark the container as essential.
@@ -244,7 +244,7 @@ container_definitions = <<DEFINITION
[
{
"name": "baserow_task",
- "image": "baserow/baserow:1.23.1",
+ "image": "baserow/baserow:1.23.2",
"logConfiguration": { #logs are not mandatory
"logDriver": "awslogs",
"options": {
@@ -368,7 +368,7 @@ in-tool settings, active enterprise licenses, promote other users to being staff
## Option 2) Deploying Baserow as separate services to Fargate/ECS
-The `baserow/backend:1.23.1` and `baserow/web-frontend:1.23.1` images allow you to run
+The `baserow/backend:1.23.2` and `baserow/web-frontend:1.23.2` images allow you to run
Baserow's various services as separate containers.
These images are used by the community Helm chart, our various docker-compose.yml
@@ -441,7 +441,7 @@ Alternatively [this docker-compose](https://gitlab.com/baserow/baserow/-/blob/de
This service is our HTTP REST API service. When creating the task definition you should:
-1. In the task defintion use the `baserow/backend:1.23.1` image
+1. In the task defintion use the `baserow/backend:1.23.2` image
2. Under docker configuration set `gunicorn-wsgi,--timeout,60` as the Command.
> We recommend setting the timeout of each HTTP API request to 60 seconds in the
@@ -484,7 +484,7 @@ This service is our HTTP REST API service. When creating the task definition you
This service is our Websocket API service and when configuring the task definition you
should:
-1. Use the `baserow/backend:1.23.1`
+1. Use the `baserow/backend:1.23.2`
2. Under docker configuration set `gunicorn` as the Command.
3. We recommend 2vCPUs and 4 GB of RAM per container to start with.
4. Map the container port `8000`/`TCP`
@@ -496,7 +496,7 @@ should:
This service is our asynchronous high priority task worker queue used for realtime
collaboration and sending emails.
-1. Use the `baserow/backend:1.23.1` image with `celery-worker` as the image command.
+1. Use the `baserow/backend:1.23.2` image with `celery-worker` as the image command.
2. Under docker configuration set `celery-worker` as the Command.
3. No port mappings needed.
4. We recommend 2vCPUs and 4 GB of RAM per container to start with.
@@ -509,7 +509,7 @@ This service is our asynchronous slow/low priority task worker queue for batch
processes and running potentially slow operations for users like table exports and
imports etc.
-1. Use the `baserow/backend:1.23.1` image.
+1. Use the `baserow/backend:1.23.2` image.
2. Under docker configuration set `celery-exportworker` as the Command.
3. No port mappings needed.
4. We recommend 2vCPUs and 4 GB of RAM per container to start with.
@@ -520,7 +520,7 @@ imports etc.
This service is our CRON task scheduler that can have multiple replicas deployed.
-1. Use the `baserow/backend:1.23.1` image.
+1. Use the `baserow/backend:1.23.2` image.
2. Under docker configuration set `celery-beat` as the Command.
3. No port mapping needed.
4. We recommend 1vCPUs and 3 GB of RAM per container to start with.
@@ -537,7 +537,7 @@ This service is our CRON task scheduler that can have multiple replicas deployed
Finally, this service is used for server side rendering and serving the frontend of
Baserow.
-1. Use the `baserow/web-frontend:1.23.1` image with no arguments needed.
+1. Use the `baserow/web-frontend:1.23.2` image with no arguments needed.
2. Map the container port `3000`
3. We recommend 2vCPUs and 4 GB of RAM per container to start with.
4. Mark the container as essential.
diff --git a/docs/installation/install-on-cloudron.md b/docs/installation/install-on-cloudron.md
index 32ebf8042..17be014c0 100644
--- a/docs/installation/install-on-cloudron.md
+++ b/docs/installation/install-on-cloudron.md
@@ -46,7 +46,7 @@ $ cd baserow/deploy/cloudron
After that you can install the Baserow Cloudron app by executing the following commands.
```
-$ cloudron install -l baserow.{YOUR_DOMAIN} --image baserow/cloudron:1.23.1
+$ cloudron install -l baserow.{YOUR_DOMAIN} --image baserow/cloudron:1.23.2
App is being installed.
...
App is installed.
@@ -89,7 +89,7 @@ the `baserow/deploy/cloudron` folder, you can upgrade your cloudron baserow serv
the latest version by running the following command:
```
-cloudron update --app {YOUR_APP_ID} --image baserow/cloudron:1.23.1
+cloudron update --app {YOUR_APP_ID} --image baserow/cloudron:1.23.2
```
> Note that you must replace the image with the most recent image of Baserow. The
diff --git a/docs/installation/install-on-digital-ocean.md b/docs/installation/install-on-digital-ocean.md
index 2d6a1ed2c..7f447d41a 100644
--- a/docs/installation/install-on-digital-ocean.md
+++ b/docs/installation/install-on-digital-ocean.md
@@ -51,7 +51,7 @@ Navigate to the `Apps` page in the left sidebar of your Digital Ocean dashboard.
on `Create App`, select `Docker Hub`, and fill out the following:
Repository: `baserow/baserow`
-Image tag or digest: `1.23.1`
+Image tag or digest: `1.23.2`
Click on `Next`, then on the `Edit` button of the `baserow-baserow` web service. Here
you must change the HTTP Port to 80, and then click on `Back`. Click on the `Next`
@@ -124,7 +124,7 @@ environment.
In order to update the Baserow version, you simply need to replace the image tag.
Navigate to the `Settings` tag of your created app, click on the `baserow-baserow`
component, then click on the `Edit` button next to source, change the `Image tag` into
-the desired version (latest is `1.23.1`), and click on save. The app will redeploy
+the desired version (latest is `1.23.2`), and click on save. The app will redeploy
with the latest version.
## External email server
diff --git a/docs/installation/install-on-ubuntu.md b/docs/installation/install-on-ubuntu.md
index 8cf7eb209..a6e760591 100644
--- a/docs/installation/install-on-ubuntu.md
+++ b/docs/installation/install-on-ubuntu.md
@@ -34,7 +34,7 @@ docker run -e BASEROW_PUBLIC_URL=http://localhost \
-v baserow_data:/baserow/data \
-p 80:80 \
-p 443:443 \
-baserow/baserow:1.23.1
+baserow/baserow:1.23.2
# Watch the logs for Baserow to come available by running:
docker logs baserow
```
@@ -147,7 +147,7 @@ docker run \
-v /baserow/media:/baserow/data/media \
-p 80:80 \
-p 443:443 \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
# Check the logs and wait for Baserow to become available
docker logs baserow
```
diff --git a/docs/installation/install-using-standalone-images.md b/docs/installation/install-using-standalone-images.md
index f6f570faf..9ad62d71d 100644
--- a/docs/installation/install-using-standalone-images.md
+++ b/docs/installation/install-using-standalone-images.md
@@ -10,9 +10,9 @@
Baserow consists of a number of services, two of which are built and provided as
separate standalone images by us:
-* `baserow/backend:1.23.1` which by default starts the Gunicorn Django backend server
+* `baserow/backend:1.23.2` which by default starts the Gunicorn Django backend server
for Baserow but is also used to start the celery workers and celery beat services.
-* `baserow/web-frontend:1.23.1` which is a Nuxt server providing Server Side rendering
+* `baserow/web-frontend:1.23.2` which is a Nuxt server providing Server Side rendering
for the website.
If you want to use your own container orchestration software like Kubernetes then these
@@ -27,10 +27,10 @@ in the root of our repository.
These are all the services you need to set up to run a Baserow using the standalone
images:
-* `baserow/backend:1.23.1` (default command is `gunicorn`)
-* `baserow/backend:1.23.1` with command `celery-worker`
-* `baserow/backend:1.23.1` with command `celery-export-worker`
-* `baserow/web-frontend:1.23.1` (default command is `nuxt-local`)
+* `baserow/backend:1.23.2` (default command is `gunicorn`)
+* `baserow/backend:1.23.2` with command `celery-worker`
+* `baserow/backend:1.23.2` with command `celery-export-worker`
+* `baserow/web-frontend:1.23.2` (default command is `nuxt-local`)
* A postgres database
* A redis server
diff --git a/docs/installation/install-with-docker-compose.md b/docs/installation/install-with-docker-compose.md
index 86b491a99..d90cc519c 100644
--- a/docs/installation/install-with-docker-compose.md
+++ b/docs/installation/install-with-docker-compose.md
@@ -16,7 +16,7 @@ version: "3.4"
services:
baserow:
container_name: baserow
- image: baserow/baserow:1.23.1
+ image: baserow/baserow:1.23.2
environment:
BASEROW_PUBLIC_URL: 'http://localhost'
ports:
diff --git a/docs/installation/install-with-docker.md b/docs/installation/install-with-docker.md
index c25a09b43..fc0852929 100644
--- a/docs/installation/install-with-docker.md
+++ b/docs/installation/install-with-docker.md
@@ -27,7 +27,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
* Change `BASEROW_PUBLIC_URL` to `https://YOUR_DOMAIN` or `http://YOUR_IP` to enable
@@ -50,7 +50,7 @@ docker run \
## Image Feature Overview
-The `baserow/baserow:1.23.1` image by default runs all of Baserow's various services in
+The `baserow/baserow:1.23.2` image by default runs all of Baserow's various services in
a single container for maximum ease of use.
> This image is designed for simple single server deployments or simple container
@@ -156,7 +156,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### Behind a reverse proxy already handling ssl
@@ -169,7 +169,7 @@ docker run \
-v baserow_data:/baserow/data \
-p 80:80 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### On a nonstandard HTTP port
@@ -182,7 +182,7 @@ docker run \
-v baserow_data:/baserow/data \
-p 3001:80 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### With an external PostgresSQL server
@@ -201,7 +201,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### With an external Redis server
@@ -220,7 +220,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### With an external email server
@@ -240,7 +240,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### With a Postgresql server running on the same host as the Baserow docker container
@@ -278,7 +278,7 @@ docker run \
-v baserow_data:/baserow/data \
-p 80:80 \
-p 443:443 \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### Supply secrets using files
@@ -305,7 +305,7 @@ docker run \
-v baserow_data:/baserow/data \
-p 80:80 \
-p 443:443 \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
### Start just the embedded database
@@ -318,7 +318,7 @@ docker run -it \
--name baserow \
-p 5432:5432 \
-v baserow_data:/baserow/data \
- baserow/baserow:1.23.1 \
+ baserow/baserow:1.23.2 \
start-only-db
# Now get the password from
docker exec -it baserow cat /baserow/data/.pgpass
@@ -350,7 +350,7 @@ docker run -it \
--rm \
--name baserow \
-v baserow_data:/baserow/data \
- baserow/baserow:1.23.1 \
+ baserow/baserow:1.23.2 \
backend-cmd-with-db manage dbshell
```
@@ -473,19 +473,19 @@ the command below.
```bash
# First read the help message for this command
-docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.23.1 \
+docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.23.2 \
backend-cmd-with-db backup --help
# Stop Baserow instance
docker stop baserow
# The command below backs up Baserow to the backups folder in the baserow_data volume:
-docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.23.1 \
+docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.23.2 \
backend-cmd-with-db backup -f /baserow/data/backups/backup.tar.gz
# Or backup to a file on your host instead run something like:
docker run -it --rm -v baserow_data:/baserow/data -v $PWD:/baserow/host \
- baserow/baserow:1.23.1 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
+ baserow/baserow:1.23.2 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
```
### Restore only Baserow's Postgres Database
@@ -501,13 +501,13 @@ docker stop baserow
docker run -it --rm \
-v old_baserow_data_volume_containing_the_backup_tar_gz:/baserow/old_data \
-v new_baserow_data_volume_to_restore_into:/baserow/data \
- baserow/baserow:1.23.1 backend-cmd-with-db restore -f /baserow/old_data/backup.tar.gz
+ baserow/baserow:1.23.2 backend-cmd-with-db restore -f /baserow/old_data/backup.tar.gz
# Or to restore from a file on your host instead run something like:
docker run -it --rm \
-v baserow_data:/baserow/data -v \
$(pwd):/baserow/host \
- baserow/baserow:1.23.1 backend-cmd-with-db restore -f /baserow/host/backup.tar.gz
+ baserow/baserow:1.23.2 backend-cmd-with-db restore -f /baserow/host/backup.tar.gz
```
## Running healthchecks on Baserow
@@ -558,7 +558,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
- baserow/baserow:1.23.1
+ baserow/baserow:1.23.2
```
Or you can just store it directly in the volume at `baserow_data/env` meaning it will be
@@ -567,7 +567,7 @@ loaded whenever you mount in this data volume.
### Building your own image from Baserow
```dockerfile
-FROM baserow/baserow:1.23.1
+FROM baserow/baserow:1.23.2
# Any .sh files found in /baserow/supervisor/env/ will be sourced and loaded at startup
# useful for storing your own environment variable overrides.
diff --git a/docs/installation/install-with-k8s.md b/docs/installation/install-with-k8s.md
index 0efd64873..9c78b3f51 100644
--- a/docs/installation/install-with-k8s.md
+++ b/docs/installation/install-with-k8s.md
@@ -165,7 +165,7 @@ spec:
topologyKey: "kubernetes.io/hostname"
containers:
- name: backend-asgi
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
workingDir: /baserow
args:
- "gunicorn"
@@ -222,7 +222,7 @@ spec:
topologyKey: "kubernetes.io/hostname"
containers:
- name: backend-wsgi
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
workingDir: /baserow
args:
- "gunicorn-wsgi"
@@ -281,7 +281,7 @@ spec:
topologyKey: "kubernetes.io/hostname"
containers:
- name: backend-worker
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
args:
- "celery-worker"
imagePullPolicy: Always
@@ -298,7 +298,7 @@ spec:
- secretRef:
name: YOUR_ENV_SECRET_REF
- name: backend-export-worker
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
args:
- "celery-exportworker"
imagePullPolicy: Always
@@ -315,7 +315,7 @@ spec:
- secretRef:
name: YOUR_ENV_SECRET_REF
- name: backend-beat-worker
- image: baserow/backend:1.23.1
+ image: baserow/backend:1.23.2
args:
- "celery-beat"
imagePullPolicy: Always
@@ -356,7 +356,7 @@ spec:
topologyKey: "kubernetes.io/hostname"
containers:
- name: web-frontend
- image: baserow/web-frontend:1.23.1
+ image: baserow/web-frontend:1.23.2
args:
- nuxt
ports:
diff --git a/docs/installation/install-with-traefik.md b/docs/installation/install-with-traefik.md
index 4dfb3941b..45b02a0d6 100644
--- a/docs/installation/install-with-traefik.md
+++ b/docs/installation/install-with-traefik.md
@@ -11,7 +11,7 @@ See below for an example docker-compose file that will enable Baserow with Traef
version: "3.4"
services:
baserow:
- image: baserow/baserow:1.23.1
+ image: baserow/baserow:1.23.2
container_name: baserow
labels:
# Explicitly tell Traefik to expose this container
diff --git a/docs/installation/supported.md b/docs/installation/supported.md
index 9cb659234..a611f5045 100644
--- a/docs/installation/supported.md
+++ b/docs/installation/supported.md
@@ -10,7 +10,7 @@ Software versions are divided into the following groups:
## Web browsers
-### Baserow 1.23.1
+### Baserow 1.23.2
Browser | Supported versions | Recommended versions
----------------|--------------------|--------------------
diff --git a/docs/plugins/creation.md b/docs/plugins/creation.md
index aa7fe5e24..0ac28b9f4 100644
--- a/docs/plugins/creation.md
+++ b/docs/plugins/creation.md
@@ -122,7 +122,7 @@ containing metadata about your plugin. It should have the following JSON structu
{
"name": "TODO",
"version": "TODO",
- "supported_baserow_versions": "1.23.1",
+ "supported_baserow_versions": "1.23.2",
"plugin_api_version": "0.0.1-alpha",
"description": "TODO",
"author": "TODO",
diff --git a/docs/plugins/installation.md b/docs/plugins/installation.md
index 3656664ab..c547c93e6 100644
--- a/docs/plugins/installation.md
+++ b/docs/plugins/installation.md
@@ -36,7 +36,7 @@ build your own image based off the Baserow all-in-one image.
4. Next copy the contents shown into your `Dockerfile`
```dockerfile
-FROM baserow/baserow:1.23.1
+FROM baserow/baserow:1.23.2
# You can install a plugin found in a git repo:
RUN /baserow/plugins/install_plugin.sh \
@@ -70,9 +70,9 @@ RUN /baserow/plugins/install_plugin.sh \
5. Choose which of the `RUN` commands you'd like to use to install your plugins and
delete the rest, replace the example URLs with ones pointing to your plugin.
6. Now build your custom Baserow with the plugin installed by running:
- `docker build -t my-customized-baserow:1.23.1 .`
+ `docker build -t my-customized-baserow:1.23.2 .`
7. Finally, you can run your new customized image just like the normal Baserow image:
- `docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.23.1`
+ `docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.23.2`
### Installing in an existing Baserow all-in-one container
@@ -111,7 +111,7 @@ docker run \
-v baserow_data:/baserow/data \
# ... All your normal launch args go here
-e BASEROW_PLUGIN_GIT_REPOS=https://example.com/example/plugin1.git,https://example.com/example/plugin2.git
- baserow:1.23.1
+ baserow:1.23.2
```
These variables will only trigger and installation when found on startup of the
@@ -120,7 +120,7 @@ container. To uninstall a plugin you must still manually follow the instructions
### Caveats when installing into an existing container
If you ever delete the container you've installed plugins into at runtime and re-create
-it, the new container is created from the `baserow/baserow:1.23.1` image which does not
+it, the new container is created from the `baserow/baserow:1.23.2` image which does not
have any plugins installed.
However, when a plugin is installed at runtime or build time it is stored in the
@@ -135,7 +135,7 @@ scratch.
### Installing into standalone Baserow service images
-Baserow also provides `baserow/backend:1.23.1` and `baserow/web-frontend:1.23.1` images
+Baserow also provides `baserow/backend:1.23.2` and `baserow/web-frontend:1.23.2` images
which only run the respective backend/celery/web-frontend services. These images are
used for more advanced self-hosted deployments like a multi-service docker-compose, k8s
etc.
@@ -145,8 +145,8 @@ used with docker run and a specified command and the plugin env vars shown above
example:
```
-docker run --rm baserow/backend:1.23.1 install-plugin ...
-docker run -e BASEROW_PLUGIN_GIT_REPOS=https://example.com/example/plugin1.git,https://example.com/example/plugin2.git --rm baserow/backend:1.23.1
+docker run --rm baserow/backend:1.23.2 install-plugin ...
+docker run -e BASEROW_PLUGIN_GIT_REPOS=https://example.com/example/plugin1.git,https://example.com/example/plugin2.git --rm baserow/backend:1.23.2
```
You can use these scripts exactly as you would in the sections above to install a plugin
@@ -169,13 +169,13 @@ associated data permanently.
[Docker install guide backup section](../installation/install-with-docker.md)
for more details on how to do this.
2. Stop your Baserow server first - `docker stop baserow`
-3. `docker run --rm -v baserow_data:/baserow/data baserow:1.23.1 uninstall-plugin plugin_name`
+3. `docker run --rm -v baserow_data:/baserow/data baserow:1.23.2 uninstall-plugin plugin_name`
4. Now the plugin has uninstalled itself and all associated data has been removed.
5. Edit your custom `Dockerfile` and remove the plugin.
-6. Rebuild your image - `docker build -t my-customized-baserow:1.23.1 .`
+6. Rebuild your image - `docker build -t my-customized-baserow:1.23.2 .`
7. Remove the old container using the old image - `docker rm baserow`
8. Run your new image with the plugin removed
- - `docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.23.1`
+ - `docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.23.2`
9. If you fail to do this if you ever recreate the container, your custom image still
has the plugin installed and the new container will start up again with the plugin
re-installed.
@@ -207,7 +207,7 @@ associated data permanently.
restart as the environment variable will still contain the old plugin. To do this you
must:
1. `docker stop baserow`
- 2. `docker run --rm -v baserow_data:/baserow/data baserow:1.23.1 uninstall-plugin plugin_name`
+ 2. `docker run --rm -v baserow_data:/baserow/data baserow:1.23.2 uninstall-plugin plugin_name`
3. Now the plugin has uninstalled itself and all associated data has been removed.
4. Finally, recreate your Baserow container by using the same `docker run` command
you launched it with, just make sure the plugin you uninstalled has been removed
@@ -222,7 +222,7 @@ check what plugins are currently installed.
docker run \
--rm \
-v baserow_data:/baserow/data \
- baserow:1.23.1 list-plugins
+ baserow:1.23.2 list-plugins
# or on a running container
diff --git a/heroku.Dockerfile b/heroku.Dockerfile
index 59a433433..f74a5e9f4 100644
--- a/heroku.Dockerfile
+++ b/heroku.Dockerfile
@@ -1,4 +1,4 @@
-ARG FROM_IMAGE=baserow/baserow:1.23.1
+ARG FROM_IMAGE=baserow/baserow:1.23.2
# This is pinned as version pinning is done by the CI setting FROM_IMAGE.
# hadolint ignore=DL3006
FROM $FROM_IMAGE as image_base
diff --git a/plugin-boilerplate/{{ cookiecutter.project_slug }}/Dockerfile b/plugin-boilerplate/{{ cookiecutter.project_slug }}/Dockerfile
index 7723aaedc..2210cfae2 100644
--- a/plugin-boilerplate/{{ cookiecutter.project_slug }}/Dockerfile
+++ b/plugin-boilerplate/{{ cookiecutter.project_slug }}/Dockerfile
@@ -1,4 +1,4 @@
-FROM baserow/baserow:1.23.1
+FROM baserow/baserow:1.23.2
COPY ./plugins/{{ cookiecutter.project_module }}/ /baserow/plugins/{{ cookiecutter.project_module }}/
RUN /baserow/plugins/install_plugin.sh --folder /baserow/plugins/{{ cookiecutter.project_module }}
diff --git a/plugin-boilerplate/{{ cookiecutter.project_slug }}/backend-dev.Dockerfile b/plugin-boilerplate/{{ cookiecutter.project_slug }}/backend-dev.Dockerfile
index 0520eaadb..9f21d5b49 100644
--- a/plugin-boilerplate/{{ cookiecutter.project_slug }}/backend-dev.Dockerfile
+++ b/plugin-boilerplate/{{ cookiecutter.project_slug }}/backend-dev.Dockerfile
@@ -1,7 +1,7 @@
# This a dev image for testing your plugin when installed into the Baserow backend image
-FROM baserow/backend:1.23.1 as base
+FROM baserow/backend:1.23.2 as base
-FROM baserow/backend:1.23.1
+FROM baserow/backend:1.23.2
USER root
diff --git a/plugin-boilerplate/{{ cookiecutter.project_slug }}/backend.Dockerfile b/plugin-boilerplate/{{ cookiecutter.project_slug }}/backend.Dockerfile
index 6e185c037..67ccd64f5 100644
--- a/plugin-boilerplate/{{ cookiecutter.project_slug }}/backend.Dockerfile
+++ b/plugin-boilerplate/{{ cookiecutter.project_slug }}/backend.Dockerfile
@@ -1,4 +1,4 @@
-FROM baserow/backend:1.23.1
+FROM baserow/backend:1.23.2
USER root
diff --git a/plugin-boilerplate/{{ cookiecutter.project_slug }}/dev.Dockerfile b/plugin-boilerplate/{{ cookiecutter.project_slug }}/dev.Dockerfile
index ae83c6f2c..52637a618 100644
--- a/plugin-boilerplate/{{ cookiecutter.project_slug }}/dev.Dockerfile
+++ b/plugin-boilerplate/{{ cookiecutter.project_slug }}/dev.Dockerfile
@@ -1,7 +1,7 @@
# This a dev image for testing your plugin when installed into the Baserow all-in-one image
-FROM baserow/baserow:1.23.1 as base
+FROM baserow/baserow:1.23.2 as base
-FROM baserow/baserow:1.23.1
+FROM baserow/baserow:1.23.2
ARG PLUGIN_BUILD_UID
ENV PLUGIN_BUILD_UID=${PLUGIN_BUILD_UID:-9999}
diff --git a/plugin-boilerplate/{{ cookiecutter.project_slug }}/plugins/{{ cookiecutter.project_module }}/baserow_plugin_info.json b/plugin-boilerplate/{{ cookiecutter.project_slug }}/plugins/{{ cookiecutter.project_module }}/baserow_plugin_info.json
index 5c5fcf84c..64d198fe1 100644
--- a/plugin-boilerplate/{{ cookiecutter.project_slug }}/plugins/{{ cookiecutter.project_module }}/baserow_plugin_info.json
+++ b/plugin-boilerplate/{{ cookiecutter.project_slug }}/plugins/{{ cookiecutter.project_module }}/baserow_plugin_info.json
@@ -1,7 +1,7 @@
{
"name": "{{ cookiecutter.project_name }}",
"version": "0.0.1",
- "supported_baserow_versions": "1.23.1",
+ "supported_baserow_versions": "1.23.2",
"plugin_api_version": "0.0.1-alpha",
"description": "TODO",
"author": "TODO",
diff --git a/plugin-boilerplate/{{ cookiecutter.project_slug }}/web-frontend-dev.Dockerfile b/plugin-boilerplate/{{ cookiecutter.project_slug }}/web-frontend-dev.Dockerfile
index e09c4dd15..20e1d17f0 100644
--- a/plugin-boilerplate/{{ cookiecutter.project_slug }}/web-frontend-dev.Dockerfile
+++ b/plugin-boilerplate/{{ cookiecutter.project_slug }}/web-frontend-dev.Dockerfile
@@ -1,6 +1,6 @@
# This a dev image for testing your plugin when installed into the Baserow web-frontend image
-FROM baserow/web-frontend:1.23.1 as base
-FROM baserow/web-frontend:1.23.1
+FROM baserow/web-frontend:1.23.2 as base
+FROM baserow/web-frontend:1.23.2
USER root
diff --git a/plugin-boilerplate/{{ cookiecutter.project_slug }}/web-frontend.Dockerfile b/plugin-boilerplate/{{ cookiecutter.project_slug }}/web-frontend.Dockerfile
index 42e7a7e7f..5632c0d26 100644
--- a/plugin-boilerplate/{{ cookiecutter.project_slug }}/web-frontend.Dockerfile
+++ b/plugin-boilerplate/{{ cookiecutter.project_slug }}/web-frontend.Dockerfile
@@ -1,4 +1,4 @@
-FROM baserow/web-frontend:1.23.1
+FROM baserow/web-frontend:1.23.2
USER root
diff --git a/web-frontend/docker/docker-entrypoint.sh b/web-frontend/docker/docker-entrypoint.sh
index 2c2026b7c..ee61659a9 100755
--- a/web-frontend/docker/docker-entrypoint.sh
+++ b/web-frontend/docker/docker-entrypoint.sh
@@ -2,7 +2,7 @@
# Bash strict mode: http://redsymbol.net/articles/unofficial-bash-strict-mode/
set -euo pipefail
-export BASEROW_VERSION="1.23.1"
+export BASEROW_VERSION="1.23.2"
BASEROW_WEBFRONTEND_PORT="${BASEROW_WEBFRONTEND_PORT:-3000}"
show_help() {
diff --git a/web-frontend/package.json b/web-frontend/package.json
index 9471eb13f..684deb5c8 100644
--- a/web-frontend/package.json
+++ b/web-frontend/package.json
@@ -1,6 +1,6 @@
{
"name": "baserow",
- "version": "1.23.1",
+ "version": "1.23.2",
"private": true,
"description": "Baserow: open source no-code database web frontend.",
"author": "Bram Wiepjes (Baserow)",