Skip to content

fix(settings): use frontend build version#231

Merged
itsDNNS merged 1 commit intomainfrom
fix/settings-build-version-source
Apr 28, 2026
Merged

fix(settings): use frontend build version#231
itsDNNS merged 1 commit intomainfrom
fix/settings-build-version-source

Conversation

@itsDNNS
Copy link
Copy Markdown
Owner

@itsDNNS itsDNNS commented Apr 28, 2026

Summary

  • use the frontend build version for Settings/About when it is baked into the frontend image
  • pass the derived app version into the frontend Docker build so split frontend/backend deployments show the active frontend build
  • scope the release-check cache by the displayed version to avoid stale update banners after upgrades

Tests

  • cd frontend && npm test -- --runTestsByPath __tests__/lib/version.test.js __tests__/components/AboutTab.test.js --runInBand
  • python3 -m pytest -q tests/test_docker_workflow.py
  • cd frontend && npm run build
  • BASE_URL=http://127.0.0.1:3000 npx playwright test e2e/tests/about-version.spec.js --project="Desktop Chrome" --project="Mobile Chrome" --reporter=line
  • git diff --check

@itsDNNS itsDNNS merged commit 718e9ce into main Apr 28, 2026
5 checks passed
@itsDNNS itsDNNS deleted the fix/settings-build-version-source branch April 28, 2026 07:27
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