Ma77Ball opened a new issue, #5836:
URL: https://github.com/apache/texera/issues/5836
### Feature Summary
After a new frontend deploy, a user with an open tab keeps running the old
bundle with no signal a new version exists; the next full navigation or reload
that reuses a stale index.html requests chunk names that no longer exist and
fails. The app already stamps a build id (Version.buildNumber,
src/environments/version.prod.ts) but only displays it
(dashboard.component.ts:87); nothing compares it at runtime.
### Proposed Solution or Design
Emit a tiny cache-busted version.json at build time (extend
build-version.js) carrying buildNumber. Add a DeploymentVersionService that
periodically fetches version.json (cache-busted) and compares it to the
compiled Version.buildNumber. On mismatch, show a non-blocking notification via
the existing NotificationService ("A new version is available, reload") with a
reload action. No forced reload, no auto-execution. Part of #5291.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
