Redash Latest Releases

v10.1.0

Released on: Nov 24, 2021

Docker Tag: redash/redash:10.1.0.b50633

Summary

This release includes fixes for three security vulnerabilities (click the links for complete details to see whether your installation is affected): - Insecure default configuration affects installations where REDASH_COOKIE_SECRET is not set explicitly (CVE-2021-41192) - SSRF vulnerability affects installations that enabled URL-loading data sources (CVE-2021-43780) - Incorrect usage of state parameter in OAuth client code affects installations where Google Login is enabled (CVE-2021-43777)

It also incorporates several fixes from master that merged after the V10.0 release.

See CHANGELOG for the full release notes.

Huge thanks to Ian Carroll and another reporter who preferred to remain anonymous for responsibly disclosing these vulnerabilities.

Upgrading

From V10.0:

Follow our standard upgrade process (reproduced below). 1. Make sure to backup your data. You only need to backup Redash’s PostgreSQL database (the database Redash stores metadata in, not the ones you might be querying) as the data in Redis is transient. 2. Change directory to /opt/redash. 3. Update /opt/redash/docker-compose.yml Redash image reference to redash/redash:10.1.0.b50633 4. Stop Redash services: docker-compose stop server scheduler scheduled_worker adhoc_worker (you might need to list additional services if you updated your configuration) 5. (No migrations are needed when upgrading from 10.0) 6. Read the Impact segment at this link. If your installation is affected, follow the instructions under the Patches heading to secure the secret fields in your database. 7. Start services with docker-compose up -d

From V9:

Follow the same steps as V10 but for step 5:

  1. Apply migration: docker-compose run --rm server manage db upgrade

From V8 or earlier

  1. Follow the complete steps outlined in the V10.0 release but use this Docker Tag in step 3: redash/redash:10.1.0.b50633
  2. Read the Impact segment at this link. If your installation is affected, follow the instructions under the Patches heading to secure the secret fields in your database.

v10.0.0

Released on: Oct 02, 2021

Docker Tag: redash/redash:10.0.0.b50363

See CHANGELOG for the full release notes.

How to Upgrade

Complete upgrade instructions for those coming from V8 -> V10 appear below.


Note: V10 is the first non-beta Redash release since V8. So we expect most users upgrading to V10 are coming from V8. The upgrade from V8->V10 is like any other, but since RQ replaced Celery in this version there are a couple extra modifications that need to be done in your docker-compose.yml.

If you already run the V9-beta release you already made these changes. You can use the standard upgrade instructions instead.


These steps are performed on the server that runs Docker.

  1. Make sure to backup your data. You only need to backup Redash’s PostgreSQL database (the database Redash stores metadata in, not the ones you might be querying) as the data in Redis is transient. Note: If you just deployed a Redash V8 AMI and have not used it, you can skip this step.
  2. cd /opt/redash
  3. Update opt/redash/docker-compose.yml to reference the docker image you want to upgrade to: redash/redash:10.0.0.b50363

142671233-76952fdb-1d0b-4f54-8825-a13cc4814874

  1. Under services.scheduler.environment omit QUEUES and WORKERS_COUNT and omit environment altogether if it is empty.

142671147-2b3d1755-01a0-4561-86d4-0fff2a3d6862 5. Under services, add a new service for general RQ jobs:

yaml worker: <<: *redash-service command: worker environment: QUEUES: "periodic emails default" WORKERS_COUNT: 1

142671560-a8263e3b-0435-4327-ae46-c669f8a21b79

  1. Stop Redash services: docker-compose stop server scheduler scheduled_worker adhoc_worker (you might need to list additional services if you defined them in your docker-compose.yml previously)
  2. Force a recreation of your containers with docker-compose up --force-recreate --build
  3. Run the necessary migrations with docker-compose run --rm server manage db upgrade
  4. Restart the containers docker-compose up -d

Dashboard URL Changes

Dashboard URLs now include the dashboard id and slug.

For example, given a dashboard with the slug account-overview and an id of 251:

Before https://redash.app/dashboards/account-overview

After https://redash.app/dashboards/251-account-overview

The dashboard can also be reached using the new /dashboard (notice this is singular) endpoint. It accepts either an ID or a slug:

Either of these will redirect to the After link above. Dashboard ID's are guaranteed to be unique. But dashboards can share the same slug. If a user visits /dashboard/<some slug> and more than one dashboard exists with that slug, they will be redirected to the earliest created dashboard with that slug.


v10.0.0-beta

Released on: Jun 21, 2021

Docker Tag: redash/redash:10.0.0-beta.b49597

See CHANGELOG for the full release notes.

Special instructions for upgrading from V8 or earlier

Typically, if you are running your own instance of Redash and wish to upgrade, you would simply modify the Docker tag in your docker-compose.yml file. Since RQ has replaced Celery in this version, there are a couple extra modifications that need to be done in your docker-compose.yml:

  1. Under services/scheduler/environment, omit QUEUES and WORKERS_COUNT (and omit environment altogether if it is empty).
  2. Under services, add a new service for general RQ jobs:

yaml worker: <<: *redash-service command: worker environment: QUEUES: "periodic emails default" WORKERS_COUNT: 1

Following that, force a recreation of your containers with docker-compose up --force-recreate --build and you should be good to go.


v9.0.0-beta

Released on: Jun 14, 2020

Docker Tag: redash/redash:9.0.0-beta.b42121.

See CHANGELOG for the full release notes.

Upgrading

Typically, if you are running your own instance of Redash and wish to upgrade, you would simply modify the Docker tag in your docker-compose.yml file. Since RQ has replaced Celery in this version, there are a couple extra modifications that need to be done in your docker-compose.yml:

  1. Under services/scheduler/environment, omit QUEUES and WORKERS_COUNT (and omit environment altogether if it is empty).
  2. Under services, add a new service for general RQ jobs:

yaml worker: <<: *redash-service command: worker environment: QUEUES: "periodic emails default" WORKERS_COUNT: 1

Following that, force a recreation of your containers with docker-compose up --force-recreate --build and you should be good to go.


v8.0.0

Released on: Oct 28, 2019

Docker Tag: redash/redash:8.0.0.b32245.

See CHANGELOG for the full release notes.