Blora Panel v0.1.0-beta.7

Blora Panel v0.1.0-beta.7

Prerelease for hands-on evaluation, not a stable release.

Changes since beta.6

• File-manager right-click handling now runs during event capture, preventing the browser's native menu even when an inner file element stops propagation.
• Replaces the previous synthetic-only regression check with a real Chromium right-click and a propagation-stopping target.

Validation boundaries

The file-manager browser suite, frontend type checking, and production build are run for this release. This prerelease does not claim stable-release readiness.

License

GPL-3.0-only. Verify each downloaded archive against SHA256SUMS; the matching source tag and component manifests accompany the release.

Blora Panel v0.1.0-beta.6

Blora Panel v0.1.0-beta.6

Prerelease for hands-on evaluation, not a stable release.

Changes since beta.5

• Replaces the browser's native right-click menu in the node file manager with a built-in file-operation menu.
• Right-clicking an item selects it and offers open, create, upload, cut/copy/paste, rename, move, copy, trash, download, compress, extract, and refresh actions.
• Existing confirmation dialogs, node authorization, version checks, and durable task handling continue to guard file mutations.

Validation boundaries

The file-manager browser suite passes 6/6, frontend type checking passes, and the production web build succeeds. Windows packages are cross-compiled; no new Windows device run is claimed. This prerelease does not claim stable-release readiness.

License

GPL-3.0-only. Verify each downloaded archive against SHA256SUMS; the matching source tag and component manifests accompany the release.

Blora Panel v0.1.0-beta.5

Blora Panel v0.1.0-beta.5 is a pre-release for hands-on evaluation. Use this release to upgrade installations that currently report beta.4.

Highlights:

• Replaces browser-native dropdowns with consistent in-app controls and adds desktop/window/tab motion with reduced-motion support.
• Moves the file manager to daemon-node scope so an operator can browse that node's filesystem independently of an instance.
• Includes related UI, API, and permission handling updates.

Assets include Linux amd64 and Windows amd64 Master/Daemon packages, the standalone web bundle, and the SDK. Verify downloads with SHA256SUMS.

Windows artifacts are cross-compiled; Windows device/runtime validation remains pending.

Blora Panel v0.1.0-beta.4

Superseded by v0.1.0-beta.5. Installations that already report beta.4 should use beta.5 for the newer source revision; the updater rejects same-version, different-revision replacements.

Blora Panel v0.1.0-beta.4 is a pre-release for hands-on evaluation.

Highlights:

• Replaces browser-native dropdowns with consistent in-app controls and adds desktop/window/tab motion with reduced-motion support.
• Moves the file manager to daemon-node scope so an operator can browse that node's filesystem independently of an instance.
• Includes related UI, API, and permission handling updates.

Assets include Linux amd64 and Windows amd64 Master/Daemon packages, the standalone web bundle, and the SDK. Verify downloads with SHA256SUMS.

Windows artifacts are cross-compiled; Windows device/runtime validation remains pending.

BloraPanel v0.1.0-beta.3

BloraPanel v0.1.0-beta.3

This prerelease allows direct HTTP access to the Master when HTTPS is disabled, including requests from remote clients. HTTPS mode remains available when enabled. The release also includes refreshed Linux and Windows amd64 binaries and the web bundle.

Downloads

• Master: Linux amd64 and Windows amd64
• Daemon: Linux amd64 and Windows amd64
• SDK and web bundles
• SHA256SUMS for integrity verification

Validation

• Focused Master source/proxy tests with race detection passed.
• Master config tests passed.
• go vet passed for the Master packages.
• Linux and Windows amd64 builds and the complete release package build passed.

Blora Panel v0.1.0-beta.2

Blora Panel v0.1.0-beta.2

Prerelease for hands-on evaluation, not a stable release.

Changes since beta.1

• Start Master and Daemon with one command and no additional arguments. Each
  reads its JSON configuration beside the installed executable; relative paths
  follow that installation directory rather than the shell working directory.
• Master defaults to local HTTP on 127.0.0.1:37861. Nginx can provide public
  HTTPS and forward the original client address and origin. Proxy-header trust
  can be restricted to configured IP/CIDR ranges with verifyProxyIPs.
• Administrators can check and apply prebuilt Release updates from Settings
  for Master and from Nodes for Daemon. The production machine does not fetch
  source or compile Go/Node applications.
• A stable launcher stages and verifies a fixed release revision, switches one
  management child at a time, and restores the previous compatible program if
  the candidate does not become ready. Daemon updates drain accepted operations
  and retain owned running instances and their independent input/log helpers.
• Update checks include archive and per-file SHA-256 digests, safe paths,
  executable identity, protocol compatibility, storage migration fingerprints,
  fresh administrator authorization and durable idempotent receipts.

Installation

Choose the Linux amd64 or Windows amd64 Master/Daemon archives. Master includes
the frontend; the separate Web and SDK archives are optional for independent
frontend hosting and extension development. Download SHA256SUMS and verify
the chosen archives before extraction.

Extract Master and Daemon into separate installation directories. Copy their
example JSON to master.json / daemon.json, create the Master's private
initial-password file, and follow START.txt and the production sections of
the English or Chinese README. There is no shared default password. External
TLS is normally handled by Nginx; never expose a backend that trusts arbitrary
forwarded headers directly to the public network.

Beta.1 does not have this update engine or metadata, so the first installation
of beta.2 requires the documented manual installation/maintenance procedure.
Subsequent compatible Releases can use the web update controls. The bundled
CORE-UPDATE.json also appears as a release asset for compatibility checks.

Validation boundaries

The final release's RELEASE-PROVENANCE.json records the fixed source, archive
digests and the checks actually completed on these build inputs. Earlier
source-specific results remain in the acceptance reports; they are not
automatically promoted to certification of this build.

• Linux online-update mechanism checks preserve the actual instance PID birth
  identity, run ID, input/log recovery and business heartbeat. Management
  connections can reconnect; interactive terminal sessions may end and browser
  uploads may need resuming.
• Windows binaries are cross-compiled and integrity-checked. The new Windows
  launcher/update/Job-keeper continuity path has not been device-tested; the
  previous 14-check Windows report covers its own earlier fixed commit.
• Online updates require compatible peer protocols and the same storage
  migration fingerprint. Incompatible schema changes, launcher changes and
  arbitrary downgrades require maintenance; there is no automatic patch chain.
• Existing update records include absolute paths. Moving an active production
  state/version tree is a separate migration, not a supported automatic rebase.
• The retained stress measurements are Chromium 38.8ms, Firefox 66ms and
  WebKit 89–132ms (last 95ms) on their recorded source. There is no universal
  50ms/100ms guarantee; the 200-line editor bulk-input limitation remains.

License

GPL-3.0-only. The matching source archive and tag accompany the binaries;
component archives include LICENSE and third-party notices.

Blora Panel v0.1.0-beta.1

Blora Panel v0.1.0-beta.1

Prerelease for initial hands-on evaluation. The project owner has not yet
personally tested the application. This build has automated and agent-run
validation; stable-release readiness is not claimed.

Included

• A Material Design 3 desktop with multiple windows/tabs, light/dark appearance,
  six palettes and independently selectable translucent materials.
• Go Master and Daemon services for nodes, instances, files, Monaco editing,
  PTY terminals, persistent tasks, monitoring, Docker/Compose and backup schedules.
• Resource permissions, immediate workspace recovery, controlled extension
  installation and a standalone SDK with reference applications.
• Bounded mixed-load latency improvements and the final Chromium rounded-window
  and terminal-toolbar rendering repairs.
• Locked dependency security patches: DOMPurify 3.4.16 and source-map-js 1.2.2.
  The original dependency versions were reviewed before packaging; the beta's
  final npm audit reports zero findings. DOMPurify's upstream fix is documented
  in its security advisory.

Downloads and installation

Choose the Master and Daemon archives for Linux amd64 or Windows amd64.
The Master archive already includes the frontend. The standalone Web archive is
for separate frontend distribution; the SDK archive is for extension developers.
The source archive contains the exact committed build inputs.

Verify SHA256SUMS, extract each component into its own directory, and read
START.txt and docs/operations/OPERATIONS.md. Initialize the Master once using
--init --password-file; there is no shared default password. Use private state
directories and matching HTTPS origins/certificates. Windows binaries are console
applications, not native Windows service executables.

Validation and limits

The source closeout includes 123 passing frontend units, backend race checks,
Linux/Windows compilation and all 51 real functional scenarios across a complete
run and independent follow-ups. Earlier complete-run failures remain visible in
the acceptance reports; this does not claim a single completely green run.
Packaged startup, SDK build/signing, stopped-state restore and compatible
development-package upgrade/rollback results are reported with this release.

• The E08 extreme eight-window workload measured Chromium 38.8ms, Firefox 66ms
  and WebKit 89–132ms (last repetition 95ms), on the recorded pre-release source.
  These are source-specific measurements, not a stable 50ms or 100ms guarantee.
• The 200-line native bulk-input scenario still takes about 10–11 seconds.
• Previous Windows Job/ConPTY and 14-check device results cover their recorded
  commits. The new Windows archives are built and integrity-checked; they have
  not been rerun on a Windows device as part of this release.
• Host-management support follows declared platform capabilities. Windows
  firewall changes/rollback are not supported. Physical Safari and every device,
  network and physical-failure combination are not certified.
• Rollback is limited to verified compatible schemas and a consistent stopped
  snapshot; arbitrary schema downgrades are not supported.

License

Blora Panel is licensed GPL-3.0-only. Every component archive contains LICENSE
and third-party notices. The version tag and source archive provide the matching
source. Dependencies retain their original license terms.

Final package verification

• Fixed source: b5d0287b49b53cafaec94ee04bdd8b115cf767b4.
• All six component archives verified: 2,418 internal manifest records, all matching current inputs, and all three Web copies identical (169 files each).
• Complete matching source archive: 1,330 tracked files. Seven downloadable archives are covered by SHA256SUMS.
• Two independent package builds: six archives and the original component checksum file byte-identical.
• Extracted beta: independent SDK build/signing, fresh Master/TLS/login, two Daemons and its own stopped-state backup/restore PASS.
• Actual RC34 → beta upgrade and compatible RC34 snapshot rollback: identities, users/grants, task receipts and resource contents PASS.
• Every owned test process stopped. Windows runtime on these new beta ZIPs remains untested; previous device evidence is not relabeled.

RELEASE-PROVENANCE.json records source/bundle identities, per-archive hashes, toolchain and validation scope. SHA-256 checks establish file integrity; these assets are not publisher-signed.

The final acceptance report records completed package checks and publication. This is a documentation-only closeout after the fixed build commit; it does not replace the beta source/tag or its archives. All nine uploaded attachments match their local exact sizes and SHA-256 digests.