Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Server to v-2024-05-13-schema-change #278

Merged
merged 1 commit into from
May 14, 2024

Conversation

yvanzo
Copy link
Contributor

@yvanzo yvanzo commented May 14, 2024

It brings MusicBrainz database schema 29 and requires manual upgrade.

See release notes for detailed upgrade steps.

Checklist

It brings MusicBrainz database schema 29 and requires manual upgrade.

See release notes for detailed upgrade steps.
@yvanzo yvanzo marked this pull request as ready for review May 14, 2024 14:56
@yvanzo yvanzo merged commit 371e419 into metabrainz:schema-change-2024-q2 May 14, 2024
@yvanzo yvanzo deleted the mbdb29 branch May 14, 2024 15:18
yvanzo added a commit that referenced this pull request May 14, 2024
* schema-change-2024-q2:
  Bump musicbrainz build sequence to 2
  MBVM-42 (2/2): Prebuild db service image
  MBVM-42 (1/2): Prebuild musicbrainz service image
  Upgrade Server to v-2024-05-13-schema-change (#278)
  Pass POSTGRES_VERSION ARG in development setup too
  Update installed extensions after Postgres upgrade
  Replace analyze_new_cluster with vacuumdb (PG 14)
  Fix copying Postgres upgrade script to container
  Fix showing server version during Postgres upgrade
  Fix compiling pg_amqp during Postgres upgrade
  Hide expected and harmless error message
  MBS-13361 (mirror): Upgrade to PostgreSQL 16
  Install Perl module dependencies with Carton
  MBS-13358 (III): Upgrade Perl version to 5.38.2
  Install cpanm from source instead of using apt-get
  Install local::lib using cpanm instead of apt-get
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants