Homepage 2.7.0 upgrade: Node 24 image, no breaking changes found

released
lab run
upgraded from
2.6.0
guest
Ubuntu 26.04 VM
tested
yes, in our lab

Summary

Homepage 2.7.0 is a small release. It adds a NetBird service widget, fixes the prometheusmetric widget so it renders only the four metrics it queries, and moves the Docker base image to Node 24. Next.js goes from 16.3.8 to 16.4.1, and Next.js middleware was migrated to its newer “proxy” form. The rest is dependency bumps and removal of the k3d development setup.

Breaking changes and deprecations

The release notes list no breaking changes or deprecations. Reported by the release notes: the base image is now Node 24 and the middleware was migrated to proxy. Neither needs any action from users in our test.

Tested in our lab

We ran Homepage with Docker Compose, config mounted at ./config, and HOMEPAGE_ALLOWED_HOSTS set.

  • Installed v2.6.0 and confirmed the page returned HTTP 200.
  • Added a custom service entry to services.yaml.
  • Ran docker compose down, changed the image tag to v2.7.0, pulled, and started again.
  • The container became healthy. The page returned 200.
  • The custom service entry was still returned by /api/services.
  • All six config files had identical checksums before and after.
  • Node went from v22.23.3 to v24.22.1 inside the container.
  • The startup log showed Next.js 16.4.1 and no lines containing “error” or “warn”.
  • A request with a host not in HOMEPAGE_ALLOWED_HOSTS got a 400. We only checked this on 2.7.0, so we can’t say whether it changed.

We did not test the new NetBird widget (no NetBird instance) or the prometheusmetric fix.

Lab log

$ docker compose down
 Container homepage Removed 
 Network hp_default Removed 
$ docker compose pull
 Image ghcr.io/gethomepage/homepage:v2.7.0 Pulled 
$ docker compose up -d
 Container homepage Started 
$ docker compose ps
NAME       IMAGE                                 COMMAND                  SERVICE    CREATED          STATUS                    PORTS
homepage   ghcr.io/gethomepage/homepage:v2.7.0   "docker-entrypoint.s…"   homepage   17 seconds ago   Up 15 seconds (healthy)   0.0.0.0:3000->3000/tcp, [::]:3000->3000/tcp
$ curl -s -o /dev/null -w "%{http_code}\n" http://localhost:3000/ -H "Host: 10.99.0.10:3000"
200
$ curl -s http://localhost:3000/api/services -H "Host: 10.99.0.10:3000"
[{"name":"Lab","services":[{"name":"Example Site","href":"https://example.com","description":"marker-entry-for-upgrade-test","weight":100,"type":"service","widgets":[]}],"groups":[]}]
$ md5sum config/*.yaml
0bf9821fd8defbe7258608ef6c2a4ec0  config/bookmarks.yaml
b0e3a27c624c1ba079b93169fddedd05  config/docker.yaml
eca6252c1369cb6f27c3daf97d5db31f  config/kubernetes.yaml
a534c5366fe2abbff7d272ec46b7531a  config/services.yaml
1cd75efbab723d2cdc28d003bfa01c65  config/settings.yaml
77dcbd8bb8e58d5f2b77b289dbda0369  config/widgets.yaml
$ docker exec homepage node --version
v24.22.1

Reported by others

Nothing beyond the release notes. We did not search issues or forums.

Verdict

Upgrade when convenient. The update was uneventful for a basic Docker setup, and the config was left alone. If you use the Prometheus metric widget or NetBird, the fixes and new widget are the reasons to move. Back up your config folder first, as always.

sources

other Homepage releases