Incorrect update notification / Version mismatch in UI (docker)

[drybx]

Hi!

I am running a pdfcraft instance using the default docker-compose.yml provided in this repository.

Whenever I open the Web UI, it indicates that an update is available:

However, the version info seems contradictory: pdfcraft claims to be running version 0.1.0 (which appears outdated), yet it states that this version was released on September 15, 2026.

Could there be an issue with how the version string is set during the build or how the updater checks for new releases?

Thanks!

[PDFCraftTool]

Hi Julius,

Thank you for reporting this issue! Your observation is spot-on.

Here is what was happening behind the scenes:

1. The 0.1.0 version: When building via docker-compose, APP_VERSION wasn't explicitly injected, causing Next.js to fall back to the default 0.1.0 placeholder in package.json. Because the release updater compares 0.1.0 against the date-tagged GitHub releases (e.g., v2026.09.15-cf714ad), it considered the instance outdated and repeatedly prompted the update dialog.
2. The confusing "Released" date: The Released: 15.9.2026 timestamp was actually the release date of the new version on GitHub, but because it was rendered inline next to Current: 0.1.0, it gave the misleading impression that version 0.1.0 was released on September 15.

Fixes Applied:

• Automatic Git Version Detection: The build process now automatically detects the latest Git commit hash and commit date (vYYYY.MM.DD-<hash>) if no manual APP_VERSION is provided.
• UI Layout Refinement: The release date has been relocated next to the new version tag in the update modal to eliminate any visual ambiguity.
• Option to Disable Update Checks: If you are running a self-hosted Docker instance and prefer not to receive desktop update prompts, you can now set DISABLE_UPDATE_CHECK: "true" in docker-compose.yml.

How to update your instance:

Please pull the latest changes from main and rebuild your containers:

git pull origin main
docker compose down
docker compose up --build -d

Once rebuilt, pdfcraft will show the correct Git-derived version matching your repository commit and will no longer falsely alert for an update.

If you have any further questions or suggestions, feel free to let us know!

[drybx]

Hi!

Thanks for looking into this. I just pulled the latest version and rebuilt the containers. Unfortunately, the issue seems to persist:

[PDFCraftTool]

Hi,

Thanks for your patience and for following up!

This issue no longer seems to reproduce on our live demo at https://pdfcraft.devtoolcafe.com/, and the fix has been verified.

Instead of building the containers locally from source, could you please try pulling and deploying the latest pre-built Docker image directly?

[drybx]

Could you share the exact docker pull command / image reference (registry, repo, tag) for the pre-built image? I don't see one documented in DEPLOYMENT.md.

[drybx]

Ah, found it.
changed my docker compose like so:

services:
  web:
    image: ghcr.io/pdfcrafttool/pdfcraft:latest
    restart: unless-stopped
    ports:
      - "8081:80"
    environment:
      - DISABLE_UPDATE_CHECK=true