mirror of
https://github.com/ever-co/ever-gauzy.git
synced 2026-10-02 01:54:50 +08:00
Ruslan KonviserandClaude Opus 5.5
cec254cd35
Every Gauzy app snap (desktop, desktop-timer, server, api-server, agent, mcp-server; amd64 and arm64) went to the Snap Store 'edge' channel only, from both the stage lane (stage-apps) and the prod lane (apps). The electron-builder snap target publishes with its own snapStore config. When the build config has no snapStore entry, that config has no channels, and the Snap Store publisher then defaults to 'edge'. Prod builds now release to 'stable' and stage builds to 'edge'. Each Linux build step appends -c.snap.publish.provider=snapStore -c.snap.publish.channels=<channel> to its yarn command. yarn adds extra arguments to the end of the script, which is the electron-builder call. The override is in the workflows because the root build scripts are shared by both lanes. Only snap.publish is overridden: a -c.publish override would be merged into the GitHub publish entry. GitHub releases, update channels and every other target are unchanged. Stage names 'edge' explicitly so each prod/stage pair still differs only in the channel. The generated snaps already use grade stable and strict confinement, and they need no store-approved plugs, so the store accepts them on stable. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>