Prep 1.10.0

README.md

@@ -17,7 +17,7 @@ tool gives you the powers of a developer without leaving your browser.
 [![Deploy to Heroku](https://www.herokucdn.com/deploy/button.svg)](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.9.1
+docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.10.0
 ```
 
 ![Baserow screenshot](docs/assets/screenshot.png "Baserow screenshot")
@@ -86,7 +86,7 @@ Created by Baserow B.V. - bram@baserow.io.
 
 Distributes under the MIT license. See `LICENSE` for more information.
 
-Version: 1.9.1
+Version: 1.10.0
 
 The official repository can be found at https://gitlab.com/bramw/baserow.
 

backend/setup.py

@@ -6,7 +6,7 @@ from setuptools import find_packages, setup
 
 PROJECT_DIR = os.path.dirname(__file__)
 REQUIREMENTS_DIR = os.path.join(PROJECT_DIR, "requirements")
-VERSION = "1.9.1"
+VERSION = "1.10.0"
 
 
 def get_requirements(env):

backend/src/baserow/config/settings/base.py

@@ -263,7 +263,7 @@ SPECTACULAR_SETTINGS = {
         "name": "MIT",
         "url": "https://gitlab.com/bramw/baserow/-/blob/master/LICENSE",
     },
-    "VERSION": "1.9.1",
+    "VERSION": "1.10.0",
     "SERVE_INCLUDE_SCHEMA": False,
     "TAGS": [
         {"name": "Settings"},

backend/src/baserow/version.py

@@ -1 +1 @@
-VERSION = "1.9.1"
+VERSION = "1.10.0"

changelog.md

@@ -2,6 +2,8 @@
 
 ## Unreleased
 
+## Released (2022-10-05 1.10.0)
+
 * Added batch create/update/delete rows endpoints. These endpoints make it possible to
   modify multiple rows at once. Currently, row created, row updated, and row deleted 
   webhooks are not triggered when using these endpoints.

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.9.1
+docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.10.0
 ```
 
 ## Quick Reference
@@ -49,7 +49,7 @@ docker run \
   -p 80:80 \
   -p 443:443 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 * Change `BASEROW_PUBLIC_URL` to `https://YOUR_DOMAIN` or `http://YOUR_IP` to enable
@@ -71,7 +71,7 @@ docker run \
 
 ## Image Feature Overview
 
-The `baserow/baserow:1.9.1` image by default runs all of Baserow's various services in a
+The `baserow/baserow:1.10.0` 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
@@ -114,7 +114,7 @@ docker run \
   -p 80:80 \
   -p 443:443 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### Behind a reverse proxy already handling ssl
@@ -127,7 +127,7 @@ docker run \
   -v baserow_data:/baserow/data \
   -p 80:80 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### On a nonstandard HTTP port
@@ -140,7 +140,7 @@ docker run \
   -v baserow_data:/baserow/data \
   -p 3001:80 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### With an external PostgresSQL server
@@ -159,7 +159,7 @@ docker run \
   -p 80:80 \
   -p 443:443 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### With an external Redis server
@@ -178,7 +178,7 @@ docker run \
   -p 80:80 \
   -p 443:443 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### With an external email server
@@ -198,7 +198,7 @@ docker run \
   -p 80:80 \
   -p 443:443 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### Start just the embedded database
@@ -211,7 +211,7 @@ docker run -it \
   --name baserow \
   -p 5432:5432 \
   -v baserow_data:/baserow/data \
-  baserow/baserow:1.9.1 \
+  baserow/baserow:1.10.0 \
   start-only-db 
 # Now get the password from
 docker exec -it baserow cat /baserow/data/.pgpass
@@ -229,7 +229,7 @@ docker run -it \
   --rm \
   --name baserow \
   -v baserow_data:/baserow/data \
-  baserow/baserow:1.9.1 \
+  baserow/baserow:1.10.0 \
   backend-cmd-with-db manage dbshell
 ```
 
@@ -286,16 +286,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.9.1 \
+docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.10.0 \
    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.9.1 \
+docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.10.0 \
    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.9.1 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
+   baserow/baserow:1.10.0 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
 ```
 
 ### Restore only Baserow's Postgres Database
@@ -364,7 +364,7 @@ docker run \
   -p 80:80 \
   -p 443:443 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 Or you can just store it directly in the volume at `baserow_data/env` meaning it will
@@ -373,7 +373,7 @@ be loaded whenever you mount in this data volume.
 ### Building your own image from Baserow
 
 ```dockerfile
-FROM baserow/baserow:1.9.1
+FROM baserow/baserow:1.10.0
 
 # Any .sh files found in /baserow/supervisor/env/ will be sourced and loaded at startup
 # useful for storing your own environment variable overrides.

deploy/all-in-one/supervisor/start.sh

@@ -14,7 +14,7 @@ cat << EOF
 ██████╔╝██║  ██║███████║███████╗██║  ██║╚██████╔╝╚███╔███╔╝
 ╚═════╝ ╚═╝  ╚═╝╚══════╝╚══════╝╚═╝  ╚═╝ ╚═════╝  ╚══╝╚══╝
 
-Version 1.9.1
+Version 1.10.0
 
 =========================================================================================
 EOF

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.9.1",
+  "version": "1.10.0",
   "healthCheckPath": "/api/_health",
   "httpPort": 80,
   "addons": {

deploy/cloudron/Dockerfile

@@ -1,4 +1,4 @@
-ARG FROM_IMAGE=baserow/baserow:1.9.1
+ARG FROM_IMAGE=baserow/baserow:1.10.0
 # This is pinned as version pinning is done by the CI setting FROM_IMAGE.
 # hadolint ignore=DL3006
 FROM $FROM_IMAGE as image_base

docker-compose.yml

@@ -181,7 +181,7 @@ services:
       local:
 
   backend:
-    image: baserow/backend:1.9.1
+    image: baserow/backend:1.10.0
     restart: unless-stopped
     environment:
       <<: *common-backend-variables
@@ -194,7 +194,7 @@ services:
       local:
 
   web-frontend:
-    image: baserow/web-frontend:1.9.1
+    image: baserow/web-frontend:1.10.0
     restart: unless-stopped
     environment:
       <<: *common-variables
@@ -204,7 +204,7 @@ services:
       local:
 
   celery:
-    image: baserow/backend:1.9.1
+    image: baserow/backend:1.10.0
     restart: unless-stopped
     environment:
       <<: *common-backend-variables
@@ -221,7 +221,7 @@ services:
       local:
 
   celery-export-worker:
-    image: baserow/backend:1.9.1
+    image: baserow/backend:1.10.0
     restart: unless-stopped
     command: celery-exportworker
     # The backend image's baked in healthcheck defaults to the django healthcheck
@@ -238,7 +238,7 @@ services:
       local:
 
   celery-beat-worker:
-    image: baserow/backend:1.9.1
+    image: baserow/backend:1.10.0
     restart: unless-stopped
     command: celery-beat
     # See https://github.com/sibson/redbeat/issues/129#issuecomment-1057478237

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.9.1
+$ cloudron install -l baserow.{YOUR_DOMAIN} --image baserow/cloudron:1.10.0
 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.9.1
+cloudron update --app {YOUR_APP_ID} --image baserow/cloudron:1.10.0
 ```
 
 > Note that you must replace the image with the most recent image of Baserow. The

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.9.1
+baserow/baserow:1.10.0
 # 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.9.1
+  baserow/baserow:1.10.0
 # Check the logs and wait for Baserow to become available
 docker logs baserow
 ```

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.9.1` which by default starts the Gunicorn Django backend server 
+* `baserow/backend:1.10.0` 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.9.1` which is a Nuxt server providing Server Side rendering 
+* `baserow/web-frontend:1.10.0` 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.9.1` (default command is `gunicorn`)
-* `baserow/backend:1.9.1` with command `celery-worker`
-* `baserow/backend:1.9.1` with command `celery-export-worker`
-* `baserow/web-frontend:1.9.1` (default command is `nuxt-local`)
+* `baserow/backend:1.10.0` (default command is `gunicorn`)
+* `baserow/backend:1.10.0` with command `celery-worker`
+* `baserow/backend:1.10.0` with command `celery-export-worker`
+* `baserow/web-frontend:1.10.0` (default command is `nuxt-local`)
 * A postgres database 
 * A redis server
 

docs/installation/install-with-docker.md

@@ -27,7 +27,7 @@ docker run \
   -p 80:80 \
   -p 443:443 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 * Change `BASEROW_PUBLIC_URL` to `https://YOUR_DOMAIN` or `http://YOUR_IP` to enable
@@ -49,7 +49,7 @@ docker run \
 
 ## Image Feature Overview
 
-The `baserow/baserow:1.9.1` image by default runs all of Baserow's various services in a
+The `baserow/baserow:1.10.0` 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
@@ -92,7 +92,7 @@ docker run \
   -p 80:80 \
   -p 443:443 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### Behind a reverse proxy already handling ssl
@@ -105,7 +105,7 @@ docker run \
   -v baserow_data:/baserow/data \
   -p 80:80 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### On a nonstandard HTTP port
@@ -118,7 +118,7 @@ docker run \
   -v baserow_data:/baserow/data \
   -p 3001:80 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### With an external PostgresSQL server
@@ -137,7 +137,7 @@ docker run \
   -p 80:80 \
   -p 443:443 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### With an external Redis server
@@ -156,7 +156,7 @@ docker run \
   -p 80:80 \
   -p 443:443 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### With an external email server
@@ -176,7 +176,7 @@ docker run \
   -p 80:80 \
   -p 443:443 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### With a Postgresql server running on the same host as the Baserow docker container
@@ -213,7 +213,7 @@ docker run \
   -v baserow_data:/baserow/data \
   -p 80:80 \
   -p 443:443 \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### Supply secrets using files 
@@ -239,7 +239,7 @@ docker run \
   -v baserow_data:/baserow/data \
   -p 80:80 \
   -p 443:443 \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 ### Start just the embedded database 
@@ -252,7 +252,7 @@ docker run -it \
   --name baserow \
   -p 5432:5432 \
   -v baserow_data:/baserow/data \
-  baserow/baserow:1.9.1 \
+  baserow/baserow:1.10.0 \
   start-only-db 
 # Now get the password from
 docker exec -it baserow cat /baserow/data/.pgpass
@@ -270,7 +270,7 @@ docker run -it \
   --rm \
   --name baserow \
   -v baserow_data:/baserow/data \
-  baserow/baserow:1.9.1 \
+  baserow/baserow:1.10.0 \
   backend-cmd-with-db manage dbshell
 ```
 
@@ -327,16 +327,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.9.1 \
+docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.10.0 \
    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.9.1 \
+docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.10.0 \
    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.9.1 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
+   baserow/baserow:1.10.0 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
 ```
 
 ### Restore only Baserow's Postgres Database
@@ -405,7 +405,7 @@ docker run \
   -p 80:80 \
   -p 443:443 \
   --restart unless-stopped \
-  baserow/baserow:1.9.1
+  baserow/baserow:1.10.0
 ```
 
 Or you can just store it directly in the volume at `baserow_data/env` meaning it will
@@ -415,7 +415,7 @@ be loaded whenever you mount in this data volume.
 ### Building your own image from Baserow
 
 ```dockerfile
-FROM baserow/baserow:1.9.1
+FROM baserow/baserow:1.10.0
 
 # Any .sh files found in /baserow/supervisor/env/ will be sourced and loaded at startup
 # useful for storing your own environment variable overrides.

heroku.Dockerfile

@@ -1,4 +1,4 @@
-ARG FROM_IMAGE=baserow/baserow:1.9.1
+ARG FROM_IMAGE=baserow/baserow:1.10.0
 # This is pinned as version pinning is done by the CI setting FROM_IMAGE.
 # hadolint ignore=DL3006
 FROM $FROM_IMAGE as image_base

web-frontend/package.json

@@ -1,6 +1,6 @@
 {
   "name": "baserow",
-  "version": "1.9.1",
+  "version": "1.10.0",
   "private": true,
   "description": "Baserow: open source no-code database web frontend.",
   "author": "Bram Wiepjes (Baserow)",