Enabling/disabling Package Dependencies on build or across schemes?

My app has it's debug and release schemes. A client had a specific request which meant adding a couple of Swift packages that we only use with said client, and we proceed to install the app directly on their devices; however, on our repository we've been managing this request in its own branch, planning to eventually merge it to the development and master branches, and I am unsure of what to do regarding the client's package dependencies.

Therefore, is there a way to manage which package dependencies to include when publishing to the App Store? Or is this an all or nothing situation?

Just keep a branch for that client with their customizations.

Enabling/disabling Package Dependencies on build or across schemes?
 
 
Q