Implement VERSION and COMMIT_SHA using Docker build arguments

[Copilot]

The version number displayed in the footer was hardcoded from package.json. Release builds need to inject the git tag (e.g., v6.10.7) and commit SHA into the Docker image using build arguments.

Changes

Build arguments approach

• Dockerfile accepts VERSION and COMMIT_SHA as build arguments (defaults: 0.0.0 and unknown)
• Vite's define feature injects these values as build-time constants (__APP_VERSION__, __APP_COMMIT_SHA__)
• Values are statically bundled into the client JavaScript

Docker configuration

• Dockerfile: Accepts VERSION and COMMIT_SHA build args, creates VERSION and COMMIT_SHA files, passes values to Vite as environment variables
• Dockerfile.dev: Echoes "dev" to both VERSION and COMMIT_SHA files for development

Frontend

• Updated useAppStore.ts to use build-time constants instead of package.json
• Footer displays: v{version} ({first 6 chars of commit SHA})
• Commit SHA hidden if value is "unknown"
• Created vite-env.d.ts for TypeScript declarations

GitHub workflow

• Updated .github/workflows/push-image.yml to extract version from git tag (strips "v" prefix)
• Extracts first 6 characters of commit SHA
• Passes both as build arguments to docker build

Git ignore

• Added VERSION to .gitignore

Usage

For production releases:

docker build -t dc-lineage-builder:6.10.7 . \
  --build-arg VERSION=6.10.7 \
  --build-arg COMMIT_SHA=$(git rev-parse --short HEAD)

The GitHub workflow automatically extracts and passes these values during release builds. Version and commit SHA are statically bundled into the client JavaScript during the build process.

• Fixes Version number #126

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Version number</issue_title>
<issue_description>When publishing a new release (for example, v6.10.7):

• The tag, as 6.10.7, should be baked into the docker image, as the file VERSION.

The VERSION file should be ignored by git.

When building the Dockerfile for production or dev, if no VERSION file is present, a dummy of 0.0.0 should be created to avoid non-existant file problems.

The client bundle currently displays the version number extracted from package.json in the footer. This needs to be changed to reference the newly generated file and be bundled statically in the client bundle.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Version number #126

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[edenchazard]

You misunderstood me. When the push image workflow is in process, and we are building the image, we should pass the version as the build arg to docker build. This workflow can be found at https://github.com/edenchazard/dc-lineage-builder/blob/main/.github/workflows/push-image.yml

Additionally, as a second requirement: also pass the commit reference as a build arg, and include the 6 digit commit reference in the footer, alongside where the version number is.

[edenchazard]

Don't bother with the generate.js script and invoking it in these scripts.

[Copilot]

Removed generate-version.js and its script invocations. Now using Vite's define feature with build args instead. Changes in commit 04ed0bb.

[edenchazard]

@copilot Just echo a dev to the VERSION file.

[Copilot]

Updated Dockerfile.dev to echo "dev" to VERSION file (and COMMIT_SHA as well). Changes in commit 04ed0bb.

[Copilot]

You misunderstood me. When the push image workflow is in process, and we are building the image, we should pass the version as the build arg to docker build. This workflow can be found at https://...

Updated to pass VERSION and COMMIT_SHA as build args in the GitHub workflow. The footer now displays both the version and the first 6 characters of the commit SHA. Changes in commit 04ed0bb.

[edenchazard]

Honestly, robot, you were shit at this. I've had to do it myself.