Skip to content

Mathesar 0.1.6

Summary

Mathesar 0.1.6 introduces Japanese localization of the UI and adds better support for working with long text in individual record pages. Improvements for administrators include compatibility with Python 3.10 and 3.11, support for databases running PostgreSQL 16, and the removal of npm and nodejs as dependencies when installing from scratch.

See the upgrading section below for instructions on how to upgrade to this version.

This page provides a comprehensive list of all changes in the release.

Improvements

You can now configure Mathesar’s UI to display in Japanese

The language setting is stored per-user and can be modified when logging in or when editing a user. This changes the text displayed on buttons and other UI elements within Mathesar. It does not change the display of data within your database (e.g. table names, column names, and cell values). We are hoping to support more languages beyond English and Japanese eventually. Please reach out to us if your are interested in helping to add more translations!

image

#3486, #3484, #3483, #3472, #3501

Text fields now auto-expands on the record page to accommodate longer texts

Before

All text inputs on the record page had the same height, regardless of their content.

image

After

All text inputs in record page dynamically adjust to accommodate the content seamlessly.

image

#3470, #3488, #3495

Mathesar is now compatible with Python versions: 3.10 and 3.11 along with 3.9

Mathesar now officially supports Python versions 3.10 and 3.11, in addition to the existing 3.9 compatibility. This will provide great flexibility while building Mathesar from source on an OS that natively ships with relatively newer versions of Python.

#3478, #3499, #3503, #3504

Mathesar is now compatible with PostgreSQL 16

Mathesar now officially supports, and is tested against, Postgres versions 13, 14, 15 and 16.

#3480

NodeJS is no longer a requirement for building Mathesar from source

We removed NodeJS as a dependency in favour of providing users with pre-built static assest for building Mathesar from source.

#3489

Bug fix

  • Fixed connection creation failures due to schema name collisions while adding provided sample schema(s) in the database #3490

Documentation

  • Documented upgrade instructions for v0.1.6 #3507
  • 0.1.6 release notes #3506
  • Documented mathesar-debug image for Docker based installations #3513
  • Fixed upgrade instructions for v0.1.5 #3469
  • Updated Mathesar’s version number in docs #3476
  • Added MkDocs edit URI #3482
  • Removed stale code coverage badge #3491

Maintenance

  • Added a health check endpoint for Mathesar #3479
  • Bumped Django from 4.2.8 to 4.2.10 #3492
  • Removed NodeJS from Docker production image #3474
  • Post release cleanup #3463

Upgrading to Mathesar 0.1.6

For installations using Docker Compose

If you have a Docker compose installation (including one from the guided script), run the command below:

docker compose -f /etc/mathesar/docker-compose.yml up --pull always -d

Your installation directory may be different

You may need to change /etc/mathesar/ in the command above if you chose to install Mathesar to a different directory.

For installations done from scratch

If you installed Mathesar from scratch, then use these steps to upgrade your installation to 0.1.6.

  1. Go to your Mathesar installation directory

    cd xMATHESAR_INSTALLATION_DIRx
    

    Note

    Your installation directory may be different from above if you used a different directory when installing Mathesar.

  2. Pull version 0.1.6 from the repository

    git pull https://github.com/mathesar-foundation/mathesar.git
    git checkout 0.1.6
    
  3. Update Python dependencies

    pip install -r requirements-prod.txt
    
  4. Activate our virtual environment

    source ./mathesar-venv/bin/activate
    
  5. You can skip the following if you’re upgrading from versions 0.1.4 and above.

    • If you’re upgrading from versions <= 0.1.3, update your environment variables according to the the new configuration specification.
    • In particular, you must put the connection info for the internal DB into new POSTGRES_* variables. The DJANGO_DATABASE_URL variable is no longer supported.
  6. Add the environment variables to the shell before running Django commands

    export $(sudo cat .env)
    
  7. Run Django migrations

    python manage.py migrate
    
  8. Download and extract frontend assets

    wget https://github.com/mathesar-foundation/mathesar/releases/download/0.1.6/static_files.zip
    unzip static_files.zip && mv static_files mathesar/static/mathesar && rm static_files.zip
    
  9. Compile Mathesar translation files

    python manage.py compilemessages
    
  10. Update Mathesar functions on the database:

    python -m mathesar.install --skip-confirm | tee /tmp/install.py.log
    
  11. Restart the gunicorn server

    systemctl restart gunicorn