Skip to content

zWork v0.5.0-beta.5

Choose a tag to compare

View all tags
@github-actions github-actions released this 05 Jul 01:05
· 36 commits to main since this release
v0.5.0-beta.5
325b979

Download zWork for your platform:

Platform File
Linux zWork-linux-x86_64.AppImage
macOS zWork-macos-universal.dmg
Windows zWork-windows-x86_64-setup.exe

Install

Linux (recommended):

curl -fsSL https://raw.githubusercontent.com/Ryz3nPlayZ/zWork/main/scripts/install.sh | bash

Or download the .AppImage and run:

chmod +x zWork-linux-x86_64.AppImage
./zWork-linux-x86_64.AppImage

macOS (cURL - no GateKeeper prompt):

curl -fsSL https://raw.githubusercontent.com/Ryz3nPlayZ/zWork/main/scripts/install-macos.sh | bash

Or download zWork-macos-universal.dmg, open it, then drag zWork to Applications.

Windows:

irm https://raw.githubusercontent.com/Ryz3nPlayZ/zWork/main/scripts/install-windows.ps1 | iex

If SmartScreen appears, click "More info" then "Run anyway".

What's new

This is a beta build. Core features are functional but may still have issues. Feedback welcome.

Fix: revert secret store to plaintext file I/O — eliminates keychain prompts.

Fixes

  • Removed the keyring crate entirely. The secret store is back to pure plaintext file I/O (~/.zwork/secrets.json, 0o600) — exactly as it was in v0.5.0-alpha.19, before the regression was introduced. The backend no longer touches the macOS Keychain, Windows Credential Manager, or Linux Secret Service, so there are zero OS keychain authorization prompts on startup or anywhere else. This reverts the regression that was inadvertently bundled into the beta.2 release.

    Beta.3's in-process cache and beta.4's file-first-with-keychain-fallback were both over-engineered partial measures. The correct fix was to remove the keychain code altogether and return to what worked: a single plaintext file, no OS integration, no prompts.

    Secrets now live only in ~/.zwork/secrets.json. If you previously stored keys in the keychain (via a beta.2/beta.3/beta.4 build), they are not migrated — re-enter your API key once in Settings after upgrading.

Assets 10
Loading