Skip to content

fix: display the full build version in the heading and footer - #10

Merged
OKAN-SOFTWARE merged 1 commit into
mainfrom
fix/display-build-version
Oct 26, 2026
Merged

OKAN-SOFTWARE merged 1 commit into
mainfrom
fix/display-build-version

Conversation

@OKAN-SOFTWARE

Copy link
Copy Markdown
Owner

The v0.3.1 app still displayed DOCUMENT INTELLIGENCE / PREVIEW 0.3, and the footer did not identify the running build.

Populate both labels from the Maven project version during resource processing. The current build displays PREVIEW 0.3.1 and Doc2FAQ · v0.3.1 · Built for clarity. Future version bumps update both labels automatically. JavaScript and CSS remain unfiltered, and Spring runtime configuration placeholders remain intact.

Validation:

  • mvn -B -ntp clean verify: 38 Java tests passed.
  • node --test src/test/js/*.test.cjs: 12 JavaScript tests passed.
  • Started the packaged JAR and confirmed the served page contains the full version in both locations, with no unresolved version tokens.
  • In a disposable copy, changed only the Maven project version to 0.3.2 and verified both labels update to 0.3.2. JavaScript/CSS stayed unchanged and ${PORT:8080} remained intact.

After merging, rebuild and restart the app to see the updated labels. The existing published v0.3.1 JAR remains unchanged.

Populate both version labels during Maven resource processing so the interface stays aligned with the project version. Preserve JavaScript, CSS, and runtime configuration substitution, and document the build behavior.
@OKAN-SOFTWARE
OKAN-SOFTWARE merged commit 2a0eb6a into main Oct 26, 2026
2 checks passed
@OKAN-SOFTWARE
OKAN-SOFTWARE deleted the fix/display-build-version branch October 26, 2026 22:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant