Package Details: metabase 0.61.1-1

Git Clone URL: https://aur.archlinux.org/metabase.git (read-only, click to copy)
Package Base: metabase
Description: The simplest, fastest way to get business intelligence and analytics to everyone in your company
Upstream URL: https://www.metabase.com/
Licenses: AGPL
Submitter: AlphaJack
Maintainer: AlphaJack (naxels)
Last Packager: naxels
Votes: 2
Popularity: 0.000000
First Submitted: 2023-06-30 00:36 (UTC)
Last Updated: 2026-05-15 07:46 (UTC)

Dependencies (6)

Sources (6)

Latest Comments

naxels commented on 2026-01-22 08:51 (UTC)

Unfortunately the easy way to update Metabase doesn't work that well, I'm receiving notifications on Github for Metabase updates, however since they don't make them Latest releases, it's hard to capture the correct version using automation.

I prefer not to go the latest from website / unpack JAR etc route as it's more complicated, adding more steps to providing an updated version.

It would be really helpful if Metabase just created a release for every .x update

I do agree that currently it's not ideal as you get the latest version from the time myself or AlphaJack hit's the update.sh script, which could potentially get you a lower point release than is the actual latest

Terrance commented on 2026-01-18 14:15 (UTC)

The use of v$pkgver.x in the URL I think is still causing trouble, as additional patch releases replace the artifact here -- I'm currently getting v0.58.1.3 (according to version.properties inside the JAR) from the source URL as-is, which doesn't match the checksum.

Changing the URL to just use v$pkgver obtains the expected v0.58.1, though that doesn't match the current checksum either.

naxels commented on 2025-12-06 14:03 (UTC)

Thanks for pointing that out! I've updated the update script to the version specific URL

Terrance commented on 2025-12-02 19:56 (UTC)

The latest download from Metabase's website is apparently still on (or has been rolled back to) v0.57.3, causing a checksum mismatch.

I can see the updater script uses a version-specific URL to download metabase.jar -- can that be used in the PKGBUILD source URL too?