You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Release request: v0.1.2 with signed macOS PKG #143
If a full release isn't ready yet, run the Release workflow on main via workflow_dispatch with version=0.1.2-rc.1 and skip_github_release=true. A signed PKG run artifact is enough for us to start testing.
Please keep the current signing identity. The daemon's Keychain items are bound to the app's designated requirement, so a different certificate forces every enrolled device to re-enroll.
@peterj could you cut a v0.1.2 release from
main(currently 48b4df7)?We're rolling agentdesktop out through MDM and need a release-signed macOS PKG that includes the fixes merged since v0.1.1:
The only signed PKGs available today are the v0.1.1 run artifact and the #124 branch build (
0.1.2-124). Neither has these fixes.Asks, in order of preference:
main, with the workspace version bumped first (see v0.1.1 binary internally reports version 0.1.0 (Cargo.toml not bumped before release) #106;Cargo.tomlstill says 0.1.0). Attach the macOS PKG to the release if add macOS installers to the release #124 lands in time (see Release v0.1.0 missing macOS PKG installer — only raw binaries attached #77).mainviaworkflow_dispatchwithversion=0.1.2-rc.1andskip_github_release=true. A signed PKG run artifact is enough for us to start testing.Please keep the current signing identity. The daemon's Keychain items are bound to the app's designated requirement, so a different certificate forces every enrolled device to re-enroll.
Thanks!