Repository navigation
v0.0.2-beta.1
Pre-release
🌌 VoidOne v0.0.2-beta.1
The platform foundation grows.
Released: October 8, 2026 · Pre-release / Beta
VoidOne v0.0.2-beta.1 is a major milestone in the project's evolution from an early native gaming launcher into a broader native PC gaming platform foundation.
Since v0.0.1-beta.1, the project has gone through hundreds of commits covering runtime reliability, Steam discovery, database hardening, Windows packaging, security engineering, CI/CD, AI-assisted engineering infrastructure, and finally a complete rebuild of the desktop platform shell.
This release is the result of that entire engineering cycle.
🚀 Highlights
🎨 A New VoidOne Platform Shell
The desktop experience has been rebuilt around the platform direction of VoidOne.
- 🏠 New Home experience
- 🎮 Redesigned Library
- 📈 Activity section
- ⚙️ Settings section
- 📐 Compactable sidebar
- 🃏 Reworked game cards
- 🔎 Improved search and filtering
- ℹ️ Game details experience
- 🔔 Improved notification and interaction feedback
- 🧩 Reusable SVG-based UI assets
The goal is to make VoidOne feel like a native platform layer, not just another launcher window.
➕ Native Add Game
Games can now be added through a dedicated native workflow.
Supported flows
- Select a game
.exe - Select an installation folder
- Scan the selected folder for candidate executables
- Review candidates before adding them
- Store executable and working-directory information
- Configure launch arguments
Discovered executables require user confirmation before being added to the library.
🎮 Game Library & Launching
The core game-management layer has been hardened considerably.
Improvements
- ✅ Safer executable validation
- ✅ Direct executable launching
- ✅ Launch arguments
- ✅ Working-directory support
- ✅ Correct game ID propagation
- ✅ Favorite state
- ✅ Hidden games
- ✅ Improved filtering
- ✅ Play count tracking
- ✅ Last-played tracking
- ✅ Database-backed game metadata
- ✅ Better post-launch model refresh
The library is now backed by a more reliable native C++/SQLite architecture.
🟢 Steam Discovery
Steam integration has evolved substantially since the first beta.
VoidOne now includes stronger handling for:
- Steam installation locations
- Windows registry locations
- Multiple Steam libraries
libraryfolders.vdf- VDF-escaped Windows paths
- Secondary Steam libraries
- Bounded executable discovery
- Safer executable selection
- Exclusion of common installers, helpers and redistributables
Steam scanning has also moved toward a dedicated worker-thread architecture and integration-test coverage.
🗄️ Database & Persistence
SQLite has received a major reliability pass.
Improvements
- Transactional batch insertion
- Safer connection lifecycle
- Explicit database connection handling
- Migration support
- Better runtime error reporting
- Improved batch rollback behavior
- Game metadata persistence
- Regression coverage for failed batch operations
Database behavior is now much more suitable as a foundation for a larger platform-scale library.
🛡️ Runtime & Launcher Hardening
A huge amount of work since the first beta went into making the application behave like a real native runtime.
Included
- 🧩 Early startup diagnostics
- 📝 Bootstrap logging
- 💥 Windows crash/minidump handling
- 🔒 Single-instance recovery
- 🛡️ Safer executable launching
- 📦 Packaged-runtime validation
- 🔎 Dependency validation
- 🧪 Repeated startup testing
- 🚨 Fatal startup diagnostics
- 🧰 Improved runtime failure reporting
The release pipeline no longer treats “the executable compiled” as sufficient evidence that the packaged application works.
🧪 CI/CD & Quality Engineering
VoidOne's engineering pipeline has grown dramatically during the beta cycle.
Current validation includes
- CMake
- Ninja
- CTest
- MSVC x64 validation
- AddressSanitizer coverage
- CodeQL
- Dependency security checks
- Static analysis
- Windows runtime QA
- Installer validation
- Portable package validation
- Runtime dependency validation
- Full-system QA
- Repeated startup testing
- SHA-256 artifact generation
🔖 Automatic Versioning
Tagged builds derive the application version from Git tags.
v0.0.2-beta.1
↓
0.0.2-beta.1
Development builds receive an explicit development version instead of silently falling back to a hardcoded release number.
🤖 AI-Assisted Engineering
VoidOne contains an experimental AI-assisted engineering system for CI diagnosis and repair candidates.
The intended flow is:
CI failure
↓
Diagnosis
↓
Policy validation
↓
Repair candidate
↓
Deterministic validation
↓
Review
↓
Human approval
AI-generated changes are treated as untrusted output.
Automated merging remains disabled.
This engineering infrastructure is separate from the planned player-facing VoidOne Intelligence system.
🪟 Windows Release Engineering
Windows is currently the primary release platform.
The release pipeline covers:
- Toolchain initialization
- Qt deployment
- Automatic version resolution
- Release configuration
- Native build
- Automated tests
- Runtime staging
- MSVC runtime bundling
- Installer validation
- NSIS installer generation
- Portable ZIP generation
- Artifact validation
- GitHub Release publication
Release artifacts
VoidOne-Setup-x64.exeVoidOne-Portable-x64.zip
📜 Licensing
This release uses the:
VoidOne Community License v1.0
VoidOne is free and source-available, with project-specific rules governing redistribution and commercial sale of the software itself.
See LICENSE.
📈 From v0.0.1-beta.1 to v0.0.2-beta.1
This release is the result of a much larger engineering cycle than the version number might suggest.
🧪 v0.0.1-beta.1 — Beta Foundation
The first public beta established the foundation for a more serious development and release cycle.
Major areas included:
- Native C++ / Qt architecture
- QML application structure
- SQLite persistence
- CMake presets
- Windows packaging
- WiX-based installation
- Portable builds
- CI/CD automation
- Documentation
- Application diagnostics
🛠️ v0.0.1-beta.2 — Installer Transition
v0.0.1-beta.2 was a small checkpoint centered around the NSIS installer path.
It was followed by the much larger engineering cycle that ultimately produced this release.
🔥 Post-Beta Engineering Cycle
From v0.0.1-beta.2 to v0.0.2-beta.1, the repository advanced by 460 commits.
That work covered:
- Runtime hardening
- Steam discovery
- Database architecture
- Save/backup systems
- Windows packaging
- Security engineering
- CodeQL
- AddressSanitizer
- CI architecture
- AI-assisted repair infrastructure
- Runtime QA
- Release automation
- Build optimization
- Startup diagnostics
- Platform UI redesign
🌌 v0.0.2-beta.1 — Platform Rebuild
The final stage of this cycle was the complete Platform Shell and Add Game rebuild.
This is where the underlying engineering work became visible as a much more coherent VoidOne desktop experience.
⚠️ Beta Status
VoidOne is still active experimental software.
This release does not mean every planned platform feature is complete.
Still under development or planned include areas such as:
- Advanced process lifecycle tracking
- 👻 Ghost Launcher
- Deeper provider integrations
- Larger-scale library intelligence
- 🧠 VoidOne Intelligence
- Additional cross-platform work
The roadmap describes future direction and should not be interpreted as a list of completed features.
📦 Downloads
Windows x64
Recommended
Portable
Release information
| Artifact | Architecture | Type |
|---|---|---|
| VoidOne-Setup-x64.exe | Windows x64 | Installer |
| VoidOne-Portable-x64.zip | Windows x64 | Portable |
🐛 Found a Bug?
Please report reproducible issues through:
Useful reports should include:
- What happened
- What you expected
- Steps to reproduce
- Windows version
- Relevant logs or diagnostics
- Screenshots when useful
❤️ Thank You
v0.0.2-beta.1 is not just another beta build.
It represents the transition from an early launcher foundation toward the larger platform architecture VoidOne is being built around.
Still experimental.
Still evolving.
But much closer to the vision.
Your Games. Your Hardware. Your AI. Your Rules.
Built by a gamer. Engineered like a platform. Built in the open.
🔗 Links
Full Changelog
🌌 VoidOne v0.0.2-beta.1«The platform foundation grows.»
Released: October 8, 2026 · Pre-release / Beta
VoidOne "v0.0.2-beta.1" is a major milestone in the project's evolution from an early native gaming launcher into a broader native PC gaming platform foundation.
Since "v0.0.1-beta.1", the project has gone through hundreds of commits covering runtime reliability, Steam discovery, database hardening, Windows packaging, security engineering, CI/CD, AI-assisted engineering infrastructure, and finally a complete rebuild of the desktop platform shell.
This release is the result of that entire engineering cycle.
🚀 Highlights
🎨 A New VoidOne Platform Shell
The desktop experience has been rebuilt around the platform direction of VoidOne.
- 🏠 New Home experience
- 🎮 Redesigned Library
- 📈 Activity section
- ⚙️ Settings section
- 📐 Compactable sidebar
- 🃏 Reworked game cards
- 🔎 Improved search and filtering
- ℹ️ Game details experience
- 🔔 Improved notification and interaction feedback
- 🧩 Reusable SVG-based UI assets
The goal is to make VoidOne feel like a native platform layer, not just another launcher window.
➕ Native Add Game
Games can now be added through a dedicated native workflow.
Supported flows
- Select a game ".exe"
- Select an installation folder
- Scan the selected folder for candidate executables
- Review candidates before adding them
- Store executable and working-directory information
- Configure launch arguments
«Discovered executables require user confirmation before being added to the library.»
🎮 Game Library & Launching
The core game-management layer has been hardened considerably.
Improvements
- ✅ Safer executable validation
- ✅ Direct executable launching
- ✅ Launch arguments
- ✅ Working-directory support
- ✅ Correct game ID propagation
- ✅ Favorite state
- ✅ Hidden games
- ✅ Improved filtering
- ✅ Play count tracking
- ✅ Last-played tracking
- ✅ Database-backed game metadata
- ✅ Better post-launch model refresh
The library is now backed by a more reliable native C++/SQLite architecture.
🟢 Steam Discovery
Steam integration has evolved substantially since the first beta.
VoidOne now includes stronger handling for:
- Steam installation locations
- Windows registry locations
- Multiple Steam libraries
- "libraryfolders.vdf"
- VDF-escaped Windows paths
- Secondary Steam libraries
- Bounded executable discovery
- Safer executable selection
- Exclusion of common installers, helpers and redistributables
Steam scanning has also moved toward a dedicated worker-thread architecture and integration-test coverage.
🗄️ Database & Persistence
SQLite has received a major reliability pass.
Improvements
- Transactional batch insertion
- Safer connection lifecycle
- Explicit database connection handling
- Migration support
- Better runtime error reporting
- Improved batch rollback behavior
- Game metadata persistence
- Regression coverage for failed batch operations
Database behavior is now much more suitable as a foundation for a larger platform-scale library.
🛡️ Runtime & Launcher Hardening
A huge amount of work since the first beta went into making the application behave like a real native runtime.
Included
- 🧩 Early startup diagnostics
- 📝 Bootstrap logging
- 💥 Windows crash/minidump handling
- 🔒 Single-instance recovery
- 🛡️ Safer executable launching
- 📦 Packaged-runtime validation
- 🔎 Dependency validation
- 🧪 Repeated startup testing
- 🚨 Fatal startup diagnostics
- 🧰 Improved runtime failure reporting
The release pipeline no longer treats “the executable compiled” as sufficient evidence that the packaged application works.
🧪 CI/CD & Quality Engineering
VoidOne's engineering pipeline has grown dramatically during the beta cycle.
Current validation includes
- CMake
- Ninja
- CTest
- MSVC x64 validation
- AddressSanitizer coverage
- CodeQL
- Dependency security checks
- Static analysis
- Windows runtime QA
- Installer validation
- Portable package validation
- Runtime dependency validation
- Full-system QA
- Repeated startup testing
- SHA-256 artifact generation
🔖 Automatic Versioning
Tagged builds derive the application version from Git tags.
v0.0.2-beta.1
↓
0.0.2-beta.1
Development builds receive an explicit development version instead of silently falling back to a hardcoded release number.
🤖 AI-Assisted Engineering
VoidOne contains an experimental AI-assisted engineering system for CI diagnosis and repair candidates.
The intended flow is:
CI failure
↓
Diagnosis
↓
Policy validation
↓
Repair candidate
↓
Deterministic validation
↓
Review
↓
Human approval
AI-generated changes are treated as untrusted output.
Automated merging remains disabled.
This engineering infrastructure is separate from the planned player-facing VoidOne Intelligence system.
🪟 Windows Release Engineering
Windows is currently the primary release platform.
The release pipeline covers:
- Toolchain initialization
- Qt deployment
- Automatic version resolution
- Release configuration
- Native build
- Automated tests
- Runtime staging
- MSVC runtime bundling
- Installer validation
- NSIS installer generation
- Portable ZIP generation
- Artifact validation
- GitHub Release publication
Release artifacts
- "VoidOne-Setup-x64.exe"
- "VoidOne-Portable-x64.zip"
📜 Licensing
This release uses the:
VoidOne Community License v1.0
VoidOne is free and source-available, with project-specific rules governing redistribution and commercial sale of the software itself.
See ""LICENSE"" (https://github.com/VoidOne-App/VoidOne/blob/main/LICENSE).
📈 From "v0.0.1-beta.1" to "v0.0.2-beta.1"
This release is the result of a much larger engineering cycle than the version number might suggest.
🧪 "v0.0.1-beta.1" — Beta Foundation
The first public beta established the foundation for a more serious development and release cycle.
Major areas included:
- Native C++ / Qt architecture
- QML application structure
- SQLite persistence
- CMake presets
- Windows packaging
- WiX-based installation
- Portable builds
- CI/CD automation
- Documentation
- Application diagnostics
🛠️ "v0.0.1-beta.2" — Installer Transition
"v0.0.1-beta.2" was a small checkpoint centered around the NSIS installer path.
It was followed by the much larger engineering cycle that ultimately produced this release.
🔥 Post-Beta Engineering Cycle
From "v0.0.1-beta.2" to "v0.0.2-beta.1", the repository advanced by 460 commits.
That work covered:
- Runtime hardening
- Steam discovery
- Database architecture
- Save/backup systems
- Windows packaging
- Security engineering
- CodeQL
- AddressSanitizer
- CI architecture
- AI-assisted repair infrastructure
- Runtime QA
- Release automation
- Build optimization
- Startup diagnostics
- Platform UI redesign
🌌 "v0.0.2-beta.1" — Platform Rebuild
The final stage of this cycle was the complete Platform Shell and Add Game rebuild.
This is where the underlying engineering work became visible as a much more coherent VoidOne desktop experience.
VoidOne is still active experimental software.
This release does not mean every planned platform feature is complete.
Still under development or planned include areas such as:
- Advanced process lifecycle tracking
- 👻 Ghost Launcher
- Deeper provider integrations
- Larger-scale library intelligence
- 🧠 VoidOne Intelligence
- Additional cross-platform work
The roadmap describes future direction and should not be interpreted as a list of completed features.
📦 Downloads
Windows x64
Recommended
"⬇️ Download VoidOne Setup" (https://github.com/VoidOne-App/VoidOne/releases/download/v0.0.2-beta.1/VoidOne-Setup-x64.exe)
Portable
"📦 Download VoidOne Portable" (https://github.com/VoidOne-App/VoidOne/releases/download/v0.0.2-beta.1/VoidOne-Portable-x64.zip)
Release information
Artifact| Architecture| Type
"VoidOne-Setup-x64.exe"| Windows x64| Installer
"VoidOne-Portable-x64.zip"| Windows x64| Portable
🐛 Found a Bug?
Please report reproducible issues through:
"🐛 GitHub Issues" (https://github.com/VoidOne-App/VoidOne/issues)
Useful reports should include:
- What happened
- What you expected
- Steps to reproduce
- Windows version
- Relevant logs or diagnostics
- Screenshots when useful
❤️ Thank You
"v0.0.2-beta.1" is not just another beta build.
It represents the transition from an early launcher foundation toward the larger platform architecture VoidOne is being built around.
Still experimental.
Still evolving.
But much closer to the vision.
«Your Games. Your Hardware. Your AI. Your Rules.»
Built by a gamer. Engineered like a platform. Built in the open.
🔗 Links
- "⭐ Star VoidOne" (https://github.com/VoidOne-App/VoidOne)
- "📦 All Releases" (https://github.com/VoidOne-App/VoidOne/releases)
- "🐛 Issues" (https://github.com/VoidOne-App/VoidOne/issues)
- "💬 Community Discord" (https://discord.gg/KPWfGvf9VW)
- "🤝 Contributing" (https://github.com/VoidOne-App/VoidOne/blob/main/CONTRIBUTING.md)
- "🔐 Security" (https://github.com/VoidOne-App/VoidOne/blob/main/SECURITY.md)
Full Changelog
""v0.0.1-beta.1...v0.0.2-beta.1"" (v0.0.1-beta.1...v0.0.2-beta.1)