fix(lume): remove com.apple.vm.networking from release entitlements - #1075
Conversation
The com.apple.vm.networking entitlement is a restricted entitlement that requires a provisioning profile. Without one, macOS kills the binary on launch (AMFI error -413: "No matching profile found"), making lume completely unusable — even for commands that don't use bridged networking. Remove the entitlement from lume.entitlements (used by release builds) so that signed/notarized binaries work out of the box. The entitlement remains available in lume.local.entitlements for local builds where users have the appropriate provisioning profile.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing touches🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. Comment |
📦 Publishable packages changed
Add |
Summary
com.apple.vm.networkingfromlume.entitlements(used by release/notarized builds)Problem
The
com.apple.vm.networkingentitlement is a restricted entitlement that requires a matching provisioning profile. Without one, macOS's AMFI (Apple Mobile File Integrity) kills the binary immediately on launch with error-413: No matching profile found— even for commands likelume lsthat don't use bridged networking.This was introduced in the bridged networking PR and makes the v0.2.78 release completely unusable.
Fix
Remove the entitlement from the release entitlements file. The entitlement remains in
lume.local.entitlementsfor local development builds where users can provide their own provisioning profile.Test plan
lume.entitlements— binary should launch without being killedlume ls,lume run,lume serveall work normally