summaryrefslogtreecommitdiff
path: root/scripts/release/README.md
diff options
context:
space:
mode:
authorChristian Kolset <christian.kolset@gmail.com>2026-08-01 19:06:36 -0600
committerChristian Kolset <christian.kolset@gmail.com>2026-08-01 19:06:36 -0600
commit0aa59c13af65beeae104662593b21ba4d8a37789 (patch)
tree17a1e6bd92a3a236bef0bca2e11ca7a875ba6caa /scripts/release/README.md
parentbfbdd0c19910f464e779fa64cc0ec8590f8e37c1 (diff)
Rename LabDAQ → LabUI and overhaul plugin system
Branding: - Rename app, window title, file extension (.labdaq → .labui), user data dirs (~/.labui/), spec file (labdaq.spec → labui.spec), and APP_NAME throughout all source, docs, and config files Plugin system: - Plugins no longer bundled in the PyInstaller build — installed at runtime by users via Settings → Plugins → Install Plugin (zip) - PluginManager now takes user_dir + extra_scan_dirs; user plugins live in ~/.labui/plugins/, dev scan additionally covers project plugins/ - install_from_zip / uninstall / is_user_installed added to PluginManager - vendor/ dir inside plugin zips: prepended to sys.path at load time so plugins can ship their own deps without requiring pip on end-user machine - source_url field in manifest.json: shown as Download button in the missing-plugins dialog when a profile requires an absent plugin - Frozen-app pip install now targets ~/.labui/plugin_packages/ using a real system Python (sys.executable is the exe in frozen builds) Profile loading: - Profile now stores plugins_manifest snapshot (id, name, version, source_url) alongside plugins_enabled - On load, missing or dep-broken plugins trigger MissingPluginsDialog before the rest of the profile is applied; user can install from zip or download via source_url in-dialog, or cancel the load - Plugin reconciliation only enables installed plugins — missing ones are not written to enabled.json UI: - Version label added to status bar (bottom-right, muted colour) - Settings → Plugins tab: Install Plugin… button, per-plugin Remove button for user-installed plugins, live list refresh after install/remove Docs: - New docs/building.md covers the full release pipeline - docs/plugin-development.md updated for new install flow, vendoring, source_url, profile behaviour, and distribution instructions Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Diffstat (limited to 'scripts/release/README.md')
-rw-r--r--scripts/release/README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/scripts/release/README.md b/scripts/release/README.md
index 6707ca1..54c9086 100644
--- a/scripts/release/README.md
+++ b/scripts/release/README.md
@@ -18,16 +18,16 @@ root/targets/snapshot/timestamp TUF roles) and `scripts/release/repository/`
repo.** Losing the root key means you can never publish a trusted update to
existing installs again — they'd all need a fresh, non-updating reinstall.
-Rebuild once more (`pyinstaller labdaq.spec`) after this step, so the
+Rebuild once more (`pyinstaller labui.spec`) after this step, so the
freshly-generated `root.json` gets bundled into the app (see the `.spec`
file's `_root_json` check — it only bundles the file if it already exists).
## Every release
1. Bump `__version__` in `core/version.py`.
-2. `pyinstaller labdaq.spec` → produces `dist/LabDAQ/`.
+2. `pyinstaller labui.spec` → produces `dist/LabUI/`.
3. `python scripts/release/repo_release.py` → creates+signs
- `scripts/release/repository/targets/labdaq-<version>.tar.gz` and updates
+ `scripts/release/repository/targets/labui-<version>.tar.gz` and updates
the metadata files in `scripts/release/repository/metadata/`.
4. Create (first time) or reuse the GitHub Release tagged **`updates`** on
this repo, and upload every file from `scripts/release/repository/metadata/`