Description
The v0.2.0/v0.2.1 sandbox bug went undetected because nothing in the release pipeline validates the `Entitlements.plist` configuration. Adding a simple grep-gate in the release workflow prevents this specific class of error from ever reaching production again.
Current State
- `src-tauri/Entitlements.plist` is committed to the repo; CI builds with whatever it contains.
- No validation step; the first signal of a bad config is customers filing "updater doesn't work" tickets.
Suggested Fix
Verification
Automation Hints
scope: .github/workflows/release.yml; optionally scripts/validate-entitlements.sh (new)
do-not-touch: Entitlements.plist itself, src-tauri/
approach: add-validation
risk: low
max-files-changed: 2
blocked-by: none
bail-if: the workflow already has such a step we missed
Priority
Medium — a tight build-time guard that would have prevented the v0.2.0/v0.2.1 sandbox incident entirely. Cheap insurance for every future release.
Description
The v0.2.0/v0.2.1 sandbox bug went undetected because nothing in the release pipeline validates the `Entitlements.plist` configuration. Adding a simple grep-gate in the release workflow prevents this specific class of error from ever reaching production again.
Current State
Suggested Fix
Verification
Automation Hints
scope: .github/workflows/release.yml; optionally scripts/validate-entitlements.sh (new)
do-not-touch: Entitlements.plist itself, src-tauri/
approach: add-validation
risk: low
max-files-changed: 2
blocked-by: none
bail-if: the workflow already has such a step we missed
Priority
Medium — a tight build-time guard that would have prevented the v0.2.0/v0.2.1 sandbox incident entirely. Cheap insurance for every future release.