-
-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[9.0.0] PHAR version not available #175
Comments
@overtrue I've a permission denied https://github.com/overtrue/phplint/actions/runs/4164613643/jobs/7206478202#step:7:21 when create a new release (with release workflows). PHAR build was fixed; It's on upload process ! |
I just tried to re-run it and also reported the same error, the logs are as follows. https://github.com/overtrue/phplint/actions/runs/4164613643/jobs/7206478202#step:7:21 Is it because the path to the .phar file is not the right value? Build:
Publish:
|
@overtrue At the Build PHAR step inside line 10 (initialisation) we can find I'm convainced that the volume is propagated (because read-write by default) : https://docs.docker.com/storage/volumes/#populate-a-volume-using-a-container But it should not be ! |
@overtrue I'll replace current https://github.com/overtrue/phplint/blob/9.0.2/.github/workflows/build-phar.yml workflow, by the new one https://github.com/overtrue/phplint/blob/main/.github/workflows/release.yml PS: I've replaced my docker image that produce PHAR artifact in root mode, by invocation of the box-manifest PHAR version Advantage:
NOTE The draft mode (checkbox on workflow dispatch dialog box) when enable allow a chance to preview/modify before publish it definitively ! |
FYI: I'll clean-up repository, due to all my tests in few minutes, and publish the new release 9.0.3 |
@overtrue FYI : |
Summary
Release workflow did not build the PHAR version of PHPLint 9.0.0
(https://github.com/overtrue/phplint/actions/runs/4162210510/jobs/7201105513)
Expected behaviour
PHAR built
Actual behaviour
PHAR version not available
The text was updated successfully, but these errors were encountered: