Images should be named like "<name>:<version-tag>@<sha256>"

Expected string, received null

❌&nbsp;&nbsp;&nbsp;Linting failed with 2 errors and 2 warnings&nbsp;&nbsp;&nbsp;❌

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The restart policy of the container "romm-db" should be set to "on-failure".

The "icon" and "gallery" fields must be empty for new app submissions as it is being created by the Umbrel team.

The volume "${APP_DATA_DIR}/data/resources:/romm/resources" tries to mount the file/directory "/romm/data/resources", but it is not present. This can lead to permission errors!

The volume "${APP_DATA_DIR}/data/redis:/redis-data" tries to mount the file/directory "/romm/data/redis", but it is not present. This can lead to permission errors!

The volume "${APP_DATA_DIR}/data/library:/romm/library" tries to mount the file/directory "/romm/data/library", but it is not present. This can lead to permission errors!

The volume "${APP_DATA_DIR}/data/assets:/romm/assets" tries to mount the file/directory "/romm/data/assets", but it is not present. This can lead to permission errors!

The volume "${APP_DATA_DIR}/data/config:/romm/config" tries to mount the file/directory "/romm/data/config", but it is not present. This can lead to permission errors!

The volume "${APP_DATA_DIR}/data/mysql:/var/lib/mysql" tries to mount the file/directory "/romm/data/mysql", but it is not present. This can lead to permission errors!

The default container user "root" can lead to security vulnerabilities. If you are using the root user, please try to specify a different user (e.g. "1000:1000") in the compose file or try to set the UID/PUID and GID/PGID environment variables to 1000.