v-2023-10-02

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2023-05-16-mbdb28 or later, then just run:

git fetch --tags origin && \
git checkout v-2023-10-02 && \
sudo docker-compose up --build -d

Changes

• Fix slow startup of the service mq (#257)
• Upgrade MusicBrainz Server to v-2023-10-02

v-2023-09-18

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2023-05-16-mbdb28 or later, then just run:

git fetch --tags origin && \
git checkout v-2023-09-18 && \
sudo docker-compose up --build -d

Only Change

• Upgrade MusicBrainz Server to v-2023-09-18

v-2023-08-31

Update instructions

This release can be skipped if you are already running v-2023-08-28 successfully.

Assuming your checked out version of musicbrainz-docker is v-2023-05-16-mbdb28 or later, then just run:

git fetch --tags origin && \
git checkout v-2023-08-31 && \
sudo docker-compose up --build -d

Note that previous Docker images are not removed automatically, so a regular cleanup is recommended to avoid filling up your disk.

Only change

• Fix building image for MusicBrainz by upgrading Node.js dependency to v18; See #255 and MBS-13260.

v-2023-08-28

Update instructions

Note that this release has been replaced with v-2023-08-31 to fix building issues.

Assuming your checked out version of musicbrainz-docker is v-2023-05-16-mbdb28 or later, then just run:

git fetch --tags origin && \
git checkout v-2023-08-31 && \
sudo docker-compose up --build -d

Changes

• Add Italian to UI languages on mirrors
• Add Albanian and Hebrew to UI languages in development setup only (rebuilding image is recommended)
• Upgrade MusicBrainz Server to v-2023-08-28

v-2023-08-07

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2023-05-16-mbdb28 or later, then just run:

git fetch --tags origin && \
git checkout v-2023-08-07 && \
sudo docker-compose up --build -d

Only Change

• Upgrade MusicBrainz Server to v-2023-08-07

v-2023-07-10

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2023-05-16-mbdb28 or later, then just run:

git fetch --tags origin && \
git checkout v-2023-07-10 && \
sudo docker-compose up --build -d

Only Change

• Upgrade MusicBrainz Server to v-2023-07-10

v-2023-06-07

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2023-05-16-mbdb28 or later, then just run:

git fetch --tags origin && \
git checkout v-2023-06-07 && \
sudo docker-compose up --build -d

Only Change

• Upgrade MusicBrainz Server to v-2023-06-07

v-2023-05-22

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2023-05-16-mbdb28 or later, then just run:

git fetch --tags origin && \
git checkout v-2023-05-22 && \
sudo docker-compose up --build -d

Changes

• Resolve issue #251 thanks to @PeterCodar: Do not interrupt recreating the database even if it doesn’t exist
• Upgrade MusicBrainz Server to v-2023-05-22

v-2023-05-16-mbdb28

Breaking changes

This release upgrades to MusicBrainz database schema 28. It requires to run commands taking down musicbrainz service during the upgrade.

If your musicbrainz-docker is earlier than v-2022-05-17-mbdb27, you must first update to it (see its release notes) and follow the upgrade instructions below, or remove everything using sudo docker-compose down --rmi local --volumes and reinstall.

Disk space requirement has been slightly readjusted: 200 GB (or 100 GB without indexed search), system included.

Upgrade instructions

Assuming your checked out version of musicbrainz-docker is v-2022-05-17-mbdb27 or later, then:

1. Ensure you’ve replicated up to the most recent replication packet available with the old schema 27. If you’re not sure, run:

   sudo docker-compose exec musicbrainz bash -c ./admin/replication/LoadReplicationChanges

   and see what it tells you; if you’re ready to upgrade, it should say “This replication packet matches schema sequence #\28, but the database is currently at #\27.”

2. Turn off cron jobs:

   admin/configure rm replication-cron
   sudo docker-compose up -d musicbrainz

3. Switch to the new code with:

   git fetch --tags origin
   git checkout v-2023-05-16-mbdb28
   sudo docker-compose build

4. Upgrade the database schema (it may take a while to vacuum at the end, ignore the ending message about DB_SCHEMA_SEQUENCE):

   mkdir -p local/compose/ && cp -a admin/lib/upgrade-db-schema/musicbrainz-stopped.yml local/compose/
   admin/configure add local-compose-musicbrainz-stopped
   sudo docker-compose up -d musicbrainz
   sudo docker-compose exec musicbrainz upgrade-db-schema.sh

6. Turn cron jobs back on:

   admin/configure rm local-compose-musicbrainz-stopped
   admin/configure add replication-cron

7. Restart all services:

   sudo docker-compose up -d musicbrainz

Only change

• Upgrade MusicBrainz Server to v-2023-05-15-schema-change (release notes)

v-2023-05-02

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2022-05-17-mbdb27 or later, then just run:

git fetch --tags origin && \
git checkout v-2023-05-02 && \
sudo docker-compose up --build -d

Only Change

• Upgrade MusicBrainz Server to v-2023-05-02

Reminders

• The previous intermediate release musicbrainz-docker@v-2023-04-24 also resolved a regression in fetching search indexes and made some improvements related to fetching dumps. These changes will also be included when running this update.
• This is the last release before the announced database schema change on May 15.