#bookbrainz

/

      • anonnn has quit
      • 2025-10-28 30137, 2025

      • LupinIII joined the channel
      • 2025-10-28 30121, 2025

      • ApeKattQuest has quit
      • 2025-10-28 30105, 2025

      • HSOWA joined the channel
      • 2025-10-28 30108, 2025

      • G0d joined the channel
      • 2025-10-28 30143, 2025

      • prout_ has quit
      • 2025-10-28 30107, 2025

      • prout joined the channel
      • 2025-10-28 30123, 2025

      • innocuou- has quit
      • 2025-10-28 30154, 2025

      • innocuous joined the channel
      • 2025-10-28 30102, 2025

      • rayyan_seliya[m] has quit
      • 2025-10-28 30129, 2025

      • Atharv[m] has quit
      • 2025-10-28 30127, 2025

      • Deraile- has quit
      • 2025-10-28 30155, 2025

      • anonn joined the channel
      • 2025-10-28 30143, 2025

      • julian45[m] joined the channel
      • 2025-10-28 30144, 2025

      • julian45[m]
        [monkey](https://matrix.to/#/@monkey:chatbrainz.org): i imagine you're aware already, but BB seems to be pinning a *very* old elasticsearch version
      • 2025-10-28 30107, 2025

      • julian45[m]
        and although prod could be different, the postgres version seemingly indicated in the bb-site repo (12) has been EOL for almost a year
      • 2025-10-28 30104, 2025

      • monkey[m]
        Yes, the search upgrade is a big refactor project that I always find no bandwidth for. Will see if we can split it up with ansh to get it moving forward
      • 2025-10-28 30151, 2025

      • monkey[m]
        The postgres version is incorrect, it's on the same cluster as other DBs. I was just fixing that yesterday in the dockerfile
      • 2025-10-28 30124, 2025

      • monkey[m]
        (to be clear, fixing the utils version that is installed to match the cluster version [16])
      • 2025-10-28 30100, 2025

      • monkey[m]
        I'm noting down to update the PG version in docker compose files as well.