Skip to content

Releases: codalab/codabench

v1.22

27 Jan 14:40
162ef1e

Choose a tag to compare

Manual Interventions

Main Instance

Some of the changes will require a migration and collectstatic commands to be run:

docker compose build && docker compose up -d
docker compose exec django python manage.py migrate
docker compose exec django python manage.py collectstatic --no-input

There is a new environment variable for the contact email:

CONTACT_EMAIL=info@codabench.org

Make sure to add it to your .env file before launching the containers

Compute Workers

Major compute workers changes will require updating the Compute Worker images for both Docker and Podman. Podman workers will also need Podman 5.4 minimum to work on the host

New Features (Participants, Organizers, Hosters)

Improvements

Bug fix

Documentation

v1.21.1

08 Dec 15:59
36e2f0f

Choose a tag to compare

1.21.0

14 Oct 13:21
d26ef68

Choose a tag to compare

Manual Intervention

1. MinIO migration (depending on setup) (#1964)

If you are running MinIO locally (defined by .env and docker-compose.yml, you may require to follow the following MinIO upgrade instructions, to duplicate and mirror your buckets and convert them to the new format:
https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-migrate-fs-gateway.html

2. Rebuild all containers (#2025)

docker compose build && docker compose up -d

3. Django migration (#1955)

docker compose exec django ./manage.py migrate

4. Collect static files (#1982)

docker compose exec django ./manage.py collectstatic --no-input

5.Compute Workers

We have updated the compute worker codes. If you have deployed your own workers, you will need to update your images to either :latest or :cpu1.3

New Features

Bug Fixes

Changes

Full Changelog: 1.20.0...v1.21.0

1.20.0

08 Aug 07:59
e6b85e8

Choose a tag to compare

Manual Intervention needed if upgrading

Codabench Instance

If you are upgrading from a previous version, you will need to run the following commands:

docker compose build && docker compose up -d
docker compose exec django ./manage.py makemigrations
docker compose exec django ./manage.py migrate
docker compose exec django ./manage.py collectstatic --noinput

Compute workers

If you have your own compute workers, you will also need to update them. You can simply do a docker compose pull && docker compose up -d if you are still using the latest tag inside the docker-compose.yml. Otherwise, change the tag to latest then run the previous command.

New Features

Changes

Bug Fixes

Full Changelog: 1.19.0...1.20.0

1.19.0

15 May 17:08
97f45eb

Choose a tag to compare

Manual Intervention needed if upgrading

You will need to launch a migration with the following command after upgrading:

docker compose exec django ./manage.py migrate

New Features

Bug Fixes

Full Changelog: 1.18.0...1.19.0

1.18.0

09 Apr 13:23
5ab466e

Choose a tag to compare

1.17.0

10 Feb 17:33
8d6f740

Choose a tag to compare

1.16.0

16 Jan 16:11
8606b17

Choose a tag to compare

1.15.0

19 Dec 17:59
32f11d9

Choose a tag to compare

Manual Intervention needed if upgrading

You will need to recreate the docker containers if updating to this version from a previous version.

docker compose build && docker compose up -d

To avoid waiting a day for the homepage counters to update, you can also run the commands shown here

New Features

Bug Fixes

Full Changelog: 1.14.0...1.15.0

1.14.0

03 Dec 14:27
8891697

Choose a tag to compare

Manual intervention needed if upgrading

You will need Django/Postgres to compute the numbers of participants and submissions on all competitions by running a couple of commands found here.
This is part of the optimization effort to make the website smoother for everyone without losing functionality.

New Features

Optimizations

Full Changelog: 1.13.0...1.14.0