fix: improve release visibility and cache handling
This commit is contained in:
@@ -223,7 +223,38 @@ The short dialog summary is maintained in:
|
||||
static/recent_changes.json
|
||||
```
|
||||
|
||||
Keep `docs/de/recent_changes.md` as the complete release-note source and `static/recent_changes.json` as the short 3-5 item summary for the startup dialog.
|
||||
The JSON is versioned:
|
||||
|
||||
```json
|
||||
{
|
||||
"version": "v0.4-beta2",
|
||||
"items": []
|
||||
}
|
||||
```
|
||||
|
||||
The dialog loads this file in the browser and only displays the items when `static/recent_changes.json.version` matches `build_info.version`. Keep `docs/de/recent_changes.md` as the complete user-facing release-note source and `static/recent_changes.json` as the short 3-5 item summary for the currently deployed version.
|
||||
|
||||
### Browser Cache and Release Visibility
|
||||
|
||||
RollCalc uses the build identifier as a cache-busting query parameter for RollCalc-owned static assets referenced by active templates. The preferred identifier is `build_info.commit`; if it is missing or `unknown`, the app falls back to `build_info.version`.
|
||||
|
||||
Dynamic HTML responses use:
|
||||
|
||||
```text
|
||||
Cache-Control: no-cache
|
||||
```
|
||||
|
||||
This requires browser revalidation for the calculator and Help pages while allowing versioned static assets to be cached normally.
|
||||
|
||||
For each deployment, keep these sources aligned:
|
||||
|
||||
- `build_info.json`
|
||||
- `scripts/update_build_info.sh` default `VERSION`, unless overridden during deployment
|
||||
- newest section in `docs/de/recent_changes.md`
|
||||
- `version` in `static/recent_changes.json`
|
||||
|
||||
If RollCalc does not display the latest interface after an update, perform a force reload:
|
||||
`Ctrl+F5` or `Ctrl+Shift+R` on Windows/Linux, `Cmd+Shift+R` on macOS.
|
||||
|
||||
## User Manual PDF Export
|
||||
|
||||
|
||||
Reference in New Issue
Block a user