FlyEnv v4.18.3 Update Release Notes

🚀 New Features

1. Added First-Run Technology Stack Selection

FlyEnv now gives genuinely new users a guided technology-stack selector before the main workspace opens. Instead of showing the entire module catalog by default, users can start with only the technologies relevant to their work.

The new onboarding experience includes:

• Eight Stack Presets: PHP, Node.js, Java, Python, Go, .NET, Ruby, and Rust
• Multi-Stack Selection: Multiple presets can be combined, and FlyEnv enables the union of their recommended modules
• Practical Defaults: PHP is initially selected, while Startup Groups, Hosts, and Tools remain available as common utilities
• Full Control: Users can still show every module or open Settings → Modules for detailed customization
• Safe First-Run Behavior: The selector only applies to fresh installations, so existing users keep their current module visibility settings

This makes the initial FlyEnv experience more focused and reduces the cognitive load caused by modules that a new user may not need.

2. Added Drag-and-Drop Sorting for Startup Groups

Startup Group cards can now be reordered directly from their drag handles. The chosen order is stored locally and restored the next time FlyEnv opens.

The implementation also preserves the default group identity, avoids unnecessary storage writes when the order has not changed, rejects invalid reorder data, and restores the last saved order if persistence fails.

🛠️ Improvements & Bug Fixes

3. Fixed Windows Machine ID Detection for Licensing

FlyEnv now has a more resilient Windows machine ID lookup for systems where the primary UUID provider returns an empty value or fails.

The fallback process reads Windows' MachineGuid first and then tries Win32_ComputerSystemProduct.UUID, validating the result before it is used. This fixes cases where affected users could not request or activate a FlyEnv license because no machine UUID was available.

Thanks to @FunkZero for reporting the UUID issue! Discussion #606

4. Fixed Podman Machine Creation Parameters

Podman machine creation has been updated to avoid unsupported command-line parameters and to match Podman's expected configuration behavior:

• Rosetta Configuration: Rosetta support on Apple Silicon is now written to a FlyEnv-managed containers.conf.d drop-in instead of passing the invalid --rosetta initialization flag
• Disk Sizing: The disk size setting and dashboard display now consistently use GiB, with a supported range of 10–1024 GiB
• SSH Identity Handling: The unsupported --identity-path initialization argument has been removed; FlyEnv continues to display Podman's generated SSH identity as read-only information
• Configuration Compatibility: FlyEnv respects synchronized XDG_CONFIG_HOME values and preserves custom CONTAINERS_CONF configurations through Podman's override mechanism

Thanks to @YoloCyber for the contribution and detailed follow-up reports! Issue #800 · Pull Request #855 · Issue #856 · Issue #857

📦 Build & Transparency

All FlyEnv builds continue to be produced through public GitHub Actions workflows. Build logs, workflow definitions, and release artifacts remain available for inspection in the repository.

Thank you to everyone who reports issues, contributes fixes, and helps improve FlyEnv. Feedback and suggestions are always welcome through GitHub Issues and GitHub Discussions.