You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I removed the --manifest option from Application, I did not realized that the release.yml GitHub Workflow was not ready to build manifest on BOX compilation.
As I did it on all my projects, I'll fix it on this project too !
Goal
Keep a manifest (dependencies used and embedded into a PHAR distribution) up-to-date each time we compile the PHAR version with BOX project
Diagnose
When I removed the
--manifest
option from Application, I did not realized that therelease.yml
GitHub Workflow was not ready to build manifest on BOX compilation.As I did it on all my projects, I'll fix it on this project too !
Goal
Keep a manifest (dependencies used and embedded into a PHAR distribution) up-to-date each time we compile the PHAR version with BOX project
As this feature is not part of this project, I've created my spin-off project https://github.com/llaville/box-manifest that is compatible with BOX v4.
Summary
When I ask for manifest content of PHAR distribution by following command :
I got no valid contents, except an error.
Expected behaviour
Should print the manifest contents (dependencies list embedded with constraints and versions used)
Here is a preview of what we can get
console
formatSBOM JSON
formatSBOM JSON format manifest
Actual behaviour
The text was updated successfully, but these errors were encountered: