Maurice
44c92052a3
Every page was read against the code on dev. What changed: - Pages that described 4.2 behaviour: satellite view on the vector maps, the mobile journal timeline, Collab with its fifth tab, the Review badge, clustered pins on the share page, the Leaflet preset list, the strict guard on fe80::/10, the invite link tools and their scopes, the Public API scope rules, the permission count in the plugin SDK. - Features of this release that no page mentioned: videos in a journal entry, receipts on an expense, the Google transit backend, routing counters, the rating on a place, the navigation menu, car stops, the manual school holiday catalogue and its MCP tools, the Dawarich panel in the Atlas, the release notes modal, plugin frames going fullscreen, the corridor call into the search provider hook. - Statements that sent an admin the wrong way: DEFAULT_LANGUAGE is not in the Helm ConfigMap, env.PORT cannot be changed on the chart alone, the rotation script does not cover the document sync credentials, event handlers cannot broadcast, there is no per user MFA reset in the admin panel, the demo user can edit, an unparsable APP_URL stops the server. - Updating gets a section for 4.3.0: the TREK Places API as the new default, the new variables, the Overpass timeout, SSO sessions on an OIDC only instance, the migration that puts booked nights on the drive.
2.8 KiB
Admin — GitHub Releases
The GitHub tab shows the TREK release history fetched from GitHub and provides links to community resources and support options.
Support and resources
Six cards at the top of the tab link to external resources:
| Card | Link |
|---|---|
| Ko-fi | Support the project financially |
| Buy Me a Coffee | Alternative support link |
| Discord | Join the TREK community |
| Report a Bug | Open a GitHub issue with the bug report template |
| Feature Request | Open a GitHub Discussion in the feature requests category |
| Wiki | Open the GitHub Wiki |
Release timeline
Below the support cards, a chronological timeline lists GitHub releases for the liketrek/TREK repository. Each entry shows:
- Version tag (e.g.,
v2.9.14) - A Latest badge on the first (most recent) entry in the displayed list
- Release date and author
- A Show details / Hide details toggle that expands the release notes (a small Markdown subset rendered inline:
##and###headings,-or*list items, bold,codeand http(s) links; anything else is shown as plain text)
Pre-release entries are hidden unless the server has both found a newer version and is itself running a pre-release. In every other case, including a pre-release install that is already on the newest pre-release, the timeline shows stable releases only.
Releases load 10 at a time. Click Load more at the bottom of the timeline to fetch additional pages.
If the admin API request fails, the timeline section shows an error message. If the server cannot reach the GitHub API, the timeline displays no releases (the server returns an empty list rather than an error).
Version check
The server checks for available updates daily at 9 AM (server timezone, defaults to UTC) and sends an admin notification when a newer version is published. When an update is available, a banner also appears at the top of the Admin page on next load.
Results are cached for 5 minutes to avoid repeated API calls.
Release notes notice
After an update, every user is shown a release notes notice once: a modal on the desktop with what the release brought (three headline cards), a note from the maintainer, the support links and a Release notes link to the release on GitHub. Closing it keeps it closed for the version that is running; the next version brings it back once, a patch release included. It replaces the 4.0.0 notice. There is no switch for it in the admin panel.
When to check
Review the GitHub tab before performing an upgrade to read the release notes for any versions between your current install and the target version. See Updating for the upgrade procedure.