Describe the bug
@dieffrei referring to the Slack thread, this is the issue I mean.
Using the latest vlocity_cmt package (04t5c000001WQ1GAAW) leads to unforeseen errors when trying to install it on a scratch org using the sfp validate command.
It returns the following error
Manual installs using the very same package Id works on a scratch org when utilizing the sf command.
To Reproduce
Steps to reproduce the behavior:
Create a CI scratch Org, run a validation that depends on vlocity_cmt being installed.
Expected behavior
The package should get installed
Screenshots
See above.
Platform Details (please complete the following information):
Latest ghcr container, Azure DevOps.
Additional context
Wasn't able to find anything wrong in my repository as I am able to install the package very easily when using the sf command, it fails in sfp commands exclusively.
Describe the bug @dieffrei referring to the Slack thread, this is the issue I mean. Using the latest vlocity_cmt package (04t5c000001WQ1GAAW) leads to unforeseen errors when trying to install it on a scratch org using the sfp validate command.
It returns the following error
Manual installs using the very same package Id works on a scratch org when utilizing the sf command.
To Reproduce Steps to reproduce the behavior: Create a CI scratch Org, run a validation that depends on vlocity_cmt being installed.
Expected behavior The package should get installed
Screenshots See above.
Platform Details (please complete the following information): Latest ghcr container, Azure DevOps.
Additional context Wasn't able to find anything wrong in my repository as I am able to install the package very easily when using the sf command, it fails in sfp commands exclusively.