Files
hassio-addons/mealie/config.yaml
Alexandre 62bbecb465 fix(mealie): build the frontend with pnpm and the upstream lockfile (#3046)
* fix(mealie): build the frontend with pnpm and the upstream lockfile

Upstream mealie migrated frontend/ from yarn to pnpm in v3.24.0 and deleted
frontend/yarn.lock. Our builder stage kept running "yarn install
--frozen-lockfile", which silently degraded to a fresh, unpinned resolution of
every dependency. That worked until a newer vuetify 4.x release dropped the
"vuetify/labs/rules" entry point, at which point "nuxt generate" failed with:

  Rolldown failed to resolve import "vuetify/labs/rules" from
  "virtual:nuxt:.nuxt%2Fvuetify-nuxt-plugin.client.mjs"

and the v3.25.1 updater build was reverted.

Mirror upstream's docker/Dockerfile frontend stage instead: node:24, a global
pnpm@11, and "pnpm install --frozen-lockfile" against the committed
pnpm-lock.yaml, so the dependency set is the one upstream tests. Also copy the
frontend tree with "cp -a frontend/." so dotfiles such as .nuxtignore come
across, and shallow-clone the tag.

Bumps the add-on to v3.25.1, the version the updater bot could not build.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* chore: record the shipped upstream release in updater.json

Each PR publishes an upstream version the updater bot had already selected
before CI reverted its commit, but updater.json still recorded the previous one.
The updater reads upstream_version as CURRENT and enters its update path
whenever it differs from the latest tag, so its next run would process the same
release again and derive a synthetic trailing-.1 version, producing a redundant
release, a duplicate CHANGELOG entry and a wasted build.

These values are exactly what the bot itself wrote in the reverted commit; this
restores its own record for a release now being shipped rather than choosing a
new one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 07:47:32 +02:00

118 lines
2.0 KiB
YAML

arch:
- aarch64
- amd64
description: Mealie is a self hosted recipe manager and meal planner built in Vue
devices:
- /dev/dri
- /dev/dri/card0
- /dev/dri/card1
- /dev/dri/renderD128
- /dev/vchiq
- /dev/video10
- /dev/video11
- /dev/video12
- /dev/video13
- /dev/video14
- /dev/video15
- /dev/video16
- /dev/ttyUSB0
- /dev/sda
- /dev/sdb
- /dev/sdc
- /dev/sdd
- /dev/sde
- /dev/sdf
- /dev/sdg
- /dev/nvme
- /dev/nvme0
- /dev/nvme0n1
- /dev/nvme0n1p1
- /dev/nvme0n1p2
- /dev/nvme0n1p3
- /dev/nvme1n1
- /dev/nvme1n1p1
- /dev/nvme1n1p2
- /dev/nvme1n1p3
- /dev/nvme2n1
- /dev/nvme2n1p1
- /dev/nvme2n1p2
- /dev/nvme2n3p3
- /dev/mmcblk
- /dev/fuse
- /dev/sda1
- /dev/sdb1
- /dev/sdc1
- /dev/sdd1
- /dev/sde1
- /dev/sdf1
- /dev/sdg1
- /dev/sda2
- /dev/sdb2
- /dev/sdc2
- /dev/sdd2
- /dev/sde2
- /dev/sdf2
- /dev/sdg2
- /dev/sda3
- /dev/sdb3
- /dev/sda4
- /dev/sdb4
- /dev/sda5
- /dev/sda6
- /dev/sda7
- /dev/sda8
- /dev/nvme0
- /dev/nvme1
- /dev/nvme2
discovery:
- mealie
environment:
BASE_SUBPATH: /mealie/
DATA_DIR: /config
DB_ENGINE: sqlite
MAX_WORKERS: "1"
NUXT_APP_BASE_URL: /mealie/
WEB_CONCURRENCY: "2"
WEB_GUNICORN: "true"
WORKERS_PER_CORE: "0.5"
image: ghcr.io/alexbelgium/mealie-{arch}
ingress: true
map:
- addon_config:rw
- homeassistant_config:rw
- share:rw
- ssl:rw
name: Mealie
options:
env_vars: []
ALLOW_SIGNUP: true
DATA_DIR: /config
PGID: 1000
PUID: 1000
certfile: fullchain.pem
keyfile: privkey.pem
ssl: false
panel_admin: false
panel_icon: mdi:silverware-fork-knife
ports:
9001/tcp: 9090
ports_description:
9001/tcp: Web interface
schema:
env_vars:
- name: match(^[A-Za-z0-9_]+$)
value: str?
ALLOW_SIGNUP: bool
FORWARDED_ALLOW_IPS: str?
BASE_URL: str?
DATA_DIR: str?
PGID: int
PUID: int
certfile: str
keyfile: str
ssl: bool
slug: mealie
udev: true
url: https://github.com/alexbelgium/hassio-addons
version: "v3.25.1"