-
Notifications
You must be signed in to change notification settings - Fork 44
fix: chmod binaries before publishing #43
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
Conversation
Have you observed a failure that this fixes? As far as I can tell, the executables should have the correct permissions after being built, |
In the Atom CI, there is an EACCES issue which I think is fixed by this. I am running a new CI on the new version of my fork which includes this PR: |
Ah, I see, the permission is lost between Github Actions and |
The issue is not fixed yet. I am on Windows (I publish from Windows). Not sure if that is relevant. |
fb55d92
to
09f473b
Compare
@nornagon Could you merge this, pack the package and test it in a dummy folder? Because I am on Windows, I can't easily verify if the permissions change on Linux binaries. |
@aminya publishing should happen automatically, you can test it yourself after that I believe! |
It's about an hour and nothing has been published. Are you sure that the publishing is automatic? |
Ah, it looks like indeed this repo isn't set up for that. My apologies, most in the Electron organization are. On closer inspection though, it seems this PR will have no effect, because the published packages do not contain anything in [EDIT]: ah I see, we've updated the build instructions since then. Sorry, it's been a minute and I'm operating at new-dad brain levels 😅 |
The permissions might be lost when uploaded and downloaded again. This ensures they are executables before publishing.
The reason: https://github.com/actions/upload-artifact#permission-loss