ci: synchronize release configuration across builds - #22
Merged
Conversation
use a shared vite capability profile across release platforms.\n\nenable byo-key providers, align native feature gates, and bundle berdy without release-only agents.
kalvinnchau
changed the title
kalvinnchau
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Synchronizes the public release capability configuration across macOS, Windows, and Linux.
The workflow now exports one shared Vite flag set for every platform lane, including BYO-key providers. Linux derives its native feature list through the same feature-gate helper used by the other release paths, keeping renderer and Tauri capabilities aligned.
Official and custom releases no longer stage BuilderBot by default. Berdy remains bundled from the committed distro resources, while release-only agents require an explicit selection.
Regression coverage verifies the workflow capability profile, Linux feature derivation, BYO-key default, and Berdy resource contract. Validated with the release-script suites, the full Vitest suite,
just check, and the commit/push hooks.