Files
hassio-addons/postgres_17/config.yaml
Alexandre 74121509cd fix: give every addon a version Home Assistant can order (#2926)
Seventeen addons carried a config.yaml version that awesomeversion, the
library Home Assistant orders versions with, reports as UNKNOWN: text
tags such as version-bf9e0b4f or sts, LinuxServer tags such as
v26.2-ls256, and local counters written as a semver pre-release such as
15.7-47. Home Assistant cannot tell which of two such versions is newer,
so update detection depends on a compare exception rather than on
ordering, and any version that becomes partially comparable silently
stops being offered.

Each version keeps every number it carried, as a section of its own:
v26.2-ls256 becomes v26.2.256, 4.16-r0-ls95-7 becomes 4.16.0.95.7 and
5.0.0b5-3 becomes 5.0.0.5.3, so nothing that ordered the addon is lost
and no previously published version is reused. The two versions holding
no number at all use the date instead. Only config.yaml and CHANGELOG.md
change, so every addon still builds from the upstream tag recorded in
its Dockerfile and updater.json.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-08-01 18:51:31 +02:00

39 lines
824 B
YAML

arch:
- aarch64
- amd64
backup: cold
description: Postgres 17 with VectorChord support
environment:
CONFIG_LOCATION: /config/postgresql.conf
PGDATA: /config/database
hassio_api: true
hassio_role: manager
image: ghcr.io/alexbelgium/postgres_17-{arch}
init: false
map:
- addon_config:rw
- homeassistant_config:rw
- media:rw
name: Postgres 17
options:
env_vars: []
POSTGRES_PASSWORD: homeassistant
ports:
5432/tcp: 5432
ports_description:
5432/tcp: Postgres
schema:
env_vars:
- name: match(^[A-Za-z0-9_]+$)
value: str?
POSTGRES_DB: str?
POSTGRES_HOST_AUTH_METHOD: str?
POSTGRES_INITDB_ARGS: str?
POSTGRES_PASSWORD: password
POSTGRES_USER: str?
slug: postgres_latest
startup: system
udev: true
url: https://github.com/alexbelgium/hassio-addons/tree/master/postgres
version: "17.4.13"