0.2.2 Preview — Classic progress layout

Classic now matches the Idle Slayer installation/removal progress page: 126 px ring with percentage, preparation/files/verification card, 6 px progress bar and status line. Existing product artwork, other pages and the engine transaction API remain unchanged.

Four public NuGet packages and six Native AOT SDKs are included. Native build/install/installed-uninstall checks passed on Windows, macOS and Linux, x64 and arm64. Both languages/themes rendered; MusicWars additionally passed 27 lifecycle checks, an update from 0.2.1 and 16 progress-state renders.

Preview release. Archives include SHA256SUMS and validation.json.

DivineLabs Installer 0.2.1 Preview — Engine, Components & Classic

DivineLabs Installer 0.2.1 Preview

One installation engine, reusable UI components and ready-made templates.

This patch supersedes 0.2.0. It fixes omitted configuration defaults in source-generated JSON readers,
including nested branding/application defaults and legacy package/receipt metadata without a template field.
Configuration DTOs now use generated setters; rebuild embedding hosts when upgrading libraries.
Native smoke checks now build and install from a minimal JSON file and verify its defaults in the receipt.

Choose your integration

• Core: UI-independent IInstallerEngine API, typed install/uninstall requests, async work, progress, cancellation, receipt inspection and recovery. InstallAsync also updates existing installations.
• Platforms: optional Windows/macOS/Linux registration, shortcuts and installation discovery.
• Components: bindable Avalonia StepIndicator, DirectoryPicker and OperationProgressView, independent of Core, Platforms and Classic.
• Templates.Classic: the current DivineLabs design as a reusable ClassicWindow/ClassicSession library. Styles and resources stay scoped to its window.
• Config SDK: the same divinepack workflow and native standalone installer, now consuming those libraries and public API.

The four .nupkg files below are .NET 10 libraries for a local NuGet feed, including XML API documentation. They are not published to nuget.org in this preview. Native SDK archives support config-only packaging without a .NET toolchain on the application developer's machine.

Start here

• Embedding guide
• API contract
• Architecture
• Custom launcher example
• Classic host example
• Configuration

Compatibility

Classic is the default template. Config-only integration remains supported. The new builder requires runtime format 2 with explicit template identity, and rejects incompatible old runtimes before output. Use a 0.2 target SDK for cross-packaging.

The engine reads 0.1 packages/configs/receipts. Newly written metadata includes template identity; old strict readers cannot read it. Keep the new maintenance runtime when updating standalone installations. Downgrading readers or changing maintenance ownership requires an explicit migration.

Embedded hosts own license acceptance, package trust, update policy and uninstall UX. The examples disable OS integrations unless a matching standalone runtime is supplied. The in-process API is .NET 10; other languages can use the native CLI.

Verification

All six native SDKs passed contract checks, Native AOT compilation, config-driven bundle construction, silent installation and installed-uninstaller/data-retention smoke checks. Both independent hosts compiled through local-feed NuGet packages. All 36 Classic frames rendered in both languages/themes with a host-resource isolation assertion; the custom launcher also rendered. A package-based launcher was additionally published as a Windows x64 Native AOT executable locally.

Release artifacts are from source commit c2f5a7b. Checks cover SDK file hashes, native binary headers, runtime format/template/version, source commit, debug-artifact exclusion and NuGet dependency boundaries/source metadata/API XML. See SHA256SUMS.txt and validation.json.

Preview scope

Extract generated installer archives before launch. OS/native graphics dependencies remain. Single-file self-extracting delivery, MSI/PKG/DEB/RPM, signing/notarization, automatic update feeds and symlink payloads remain outside this preview. Existing transaction/recovery guarantees are preserved; arbitrary-application or production acceptance is not claimed. MIT; preserve bundled third-party notices.

DivineLabs Installer 0.2.0 Preview — superseded by 0.2.1

Superseded by 0.2.1, which fixes omitted configuration defaults and legacy metadata reading. Download 0.2.1 for new integrations.

Known issue: 0.2.0 can lose defaults for omitted JSON configuration fields, including template identity. Use fully specified configuration files, or upgrade to 0.2.1 once published. Existing artifacts are preserved unchanged.

DivineLabs Installer 0.2.0 Preview

One installation engine, reusable UI components and ready-made templates.

Choose your integration

• Core: UI-independent IInstallerEngine API, typed install/uninstall requests, async work, progress, cancellation, receipt inspection and recovery. InstallAsync also updates existing installations.
• Platforms: optional Windows/macOS/Linux registration, shortcuts and installation discovery.
• Components: bindable Avalonia StepIndicator, DirectoryPicker and OperationProgressView, independent of Core, Platforms and Classic.
• Templates.Classic: the current DivineLabs design as a reusable ClassicWindow/ClassicSession library. Styles and resources stay scoped to its window.
• Config SDK: the same divinepack workflow and native standalone installer, now consuming those libraries and public API.

The four .nupkg files below are .NET 10 libraries for a local NuGet feed, including XML API documentation. They are not published to nuget.org in this preview. Native SDK archives support config-only packaging without a .NET toolchain on the application developer's machine.

Start here

• Embedding guide
• API contract
• Architecture
• Custom launcher example
• Classic host example
• Configuration

Compatibility

Classic is the default template. Config-only integration remains supported. The new builder requires runtime format 2 with explicit template identity, and rejects incompatible old runtimes before output. Use a 0.2 target SDK for cross-packaging.

The engine reads 0.1 packages/configs/receipts. Newly written metadata includes template identity; old strict readers cannot read it. Keep the new maintenance runtime when updating standalone installations. Downgrading readers or changing maintenance ownership requires an explicit migration.

Embedded hosts own license acceptance, package trust, update policy and uninstall UX. The examples disable OS integrations unless a matching standalone runtime is supplied. The in-process API is .NET 10; other languages can use the native CLI.

Verification

All six native SDKs passed contract checks, Native AOT compilation, config-driven bundle construction, silent installation and installed-uninstaller/data-retention smoke checks. Both independent hosts compiled through local-feed NuGet packages. All 36 Classic frames rendered in both languages/themes with a host-resource isolation assertion; the custom launcher also rendered. A package-based launcher was additionally published as a Windows x64 Native AOT executable locally.

Release artifacts are from source commit bb3ba23. Checks cover SDK file hashes, native binary headers, runtime format/template/version, source commit, debug-artifact exclusion and NuGet dependency boundaries/source metadata/API XML. See SHA256SUMS.txt and validation.json.

Preview scope

Extract generated installer archives before launch. OS/native graphics dependencies remain. Single-file self-extracting delivery, MSI/PKG/DEB/RPM, signing/notarization, automatic update feeds and symlink payloads remain outside this preview. Existing transaction/recovery guarantees are preserved; arbitrary-application or production acceptance is not claimed. MIT; preserve bundled third-party notices.

DivineLabs Installer 0.1.1 Preview

DivineLabs Installer 0.1.1 Preview

Native, config-driven setup and uninstall for Windows, macOS and Linux (x64 / ARM64).

• Match the Idle Slayer caption controls: vector close, minimize, maximize and restore icons, with accessible labels.
• Refresh light/dark screenshots from the actual Avalonia interface.
• Add a GitHub Action that downloads a prebuilt SDK, checks its release SHA-256 and builds an installer without .NET tooling.
• Add a copyable application workflow, configuration/automation/troubleshooting guides, JSON editor integration and contribution templates.
• Publish documentation introductions in English, Russian, German, Spanish and Simplified Chinese. UI languages remain English and Russian.

Getting started

Download the SDK archive for your build host, extract it and keep runtime/ beside divinepack.
Run divinepack init --dir my-installer, edit the config and build your application bundle.

• Website
• Русская документация
• Configuration
• GitHub Action

Verification

All six SDKs were built with Native AOT on matching OS/architecture runners from commit fc39c06. Each passed native bundle construction, silent installation and installed-uninstaller/data-retention smoke checks. The Action wrapper independently packaged the example on all six platforms using the published 0.1.0 SDK. All 36 setup/uninstall frames rendered in English/Russian and both themes.

Release verification checked every SDK file hash, native binary headers/architectures, absence of debug artifacts and source commit. See validation.json and SHA256SUMS.txt.

Preview scope

Extract generated installer archives before launch. Native graphics/OS dependencies remain. This is not yet single-file self-extracting EXE, MSI, PKG, DEB or RPM delivery. Product executable resource branding, automatic updates, integrated signing/notarization and symlink payloads are not supported. MIT; third-party notices are included in each SDK.

DivineLabs Installer 0.1.0 Preview

First public preview of DivineLabs Installer: configuration-driven installers built with Avalonia 12 and .NET 10 Native AOT.

Native SDKs: Windows, macOS and Linux, on x64 and ARM64. Application developers use the prebuilt CLI; no .NET SDK or application-side integration is needed.

divinepack init --dir my-installer
divinepack build --config my-installer/installer.json --runtime win-x64 --output my-output

Keep the SDK's runtime directory alongside divinepack. On Windows use divinepack.exe; in Unix shells use ./divinepack when it is not on PATH.

Includes the Idle Slayer maintenance-window layout, light/dark themes, English/Russian, configurable images/colors, optional framework branding, matching uninstaller, streaming package verification, journaled updates, cancellation rollback and restart recovery. User data is preserved by default.

Each SDK was built on its matching OS/CPU and exercised through configuration generation, installer construction, application installation and its installed native uninstaller. Tests do not launch the installed application or modify real-user integration settings.

This preview ships native installer bundles: ZIP on Windows, installer .app inside ZIP on macOS, and TAR.GZ on Linux. Extract before launching. Standalone self-extracting EXE/MSI/PKG/DEB/RPM generation, online update delivery, code signing/notarization and symlink-containing payloads are outside 0.1.0. See README for platform dependencies and scope.

MIT licensed. Dependency notices and SDK checksums are included in every SDK.