Files
hassio-addons/elasticsearch/updater.json
alexbelgium 776d063161 fix(elasticsearch): upgrade to 8.19.18 with automatic data migration
The add-on reported version 8.14.3 but the shipped image was still
Elasticsearch 7.17.9 — the Dockerfile BUILD_UPSTREAM was never bumped,
and the builder uses that ARG. The homeassistant-elasticsearch
integration requires 8.14+, so configuration failed (#2849).

- Upgrade to Elasticsearch 8.19.18 (latest 8.x; 9.x cannot read indices
  created in 7.x)
- Add automatic 7.x -> 8.x data migration with a guard that aborts on
  unsupported paths (downgrade, or data more than one major behind).
  The version marker is written only after ES answers on 9200, so a
  failed upgrade never masks the true on-disk data lineage
- Default xpack.security.enabled=false to preserve plain-HTTP behavior
  the HA component expects; override via ES_SETTING_XPACK_SECURITY_ENABLED
- Fix the env_vars option, which never worked (the image has no
  s6-overlay, so the cont-init stack never ran)
- Remove the ingest-attachment plugin install (bundled since ES 8.0,
  which broke the 8.x build)
- Replace line-number-based entrypoint patching with a proper init
  script sourced via a pattern-anchored injection
- Add updater.json pinned to the 8.19 line to prevent version drift and
  accidental 9.x jumps

Fixes #2849

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-14 11:07:24 +02:00

11 lines
263 B
JSON

{
"github_fulltag": false,
"github_tagfilter": "v8.19",
"last_update": "14-07-2026",
"repository": "alexbelgium/hassio-addons",
"slug": "elasticsearch",
"source": "github",
"upstream_repo": "elastic/elasticsearch",
"upstream_version": "8.19.18"
}