Skip to content

fix: only chmod the nitro binary right after extracting it #1

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.

Sign up for GitHub

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

Merged
tobias-tengler merged 1 commit into from
Sep 2, 2026
Merged

fix: only chmod the nitro binary right after extracting it #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions src/index.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,14 +82,18 @@ export async function installNitro(version: string) {
: await tc.extractZip(downloadPath);

toolPath = await tc.cacheDir(extractPath, toolName, version);

// Only the freshly extracted binary is marked executable. A binary that is
// already in the tool cache was installed by an earlier job, possibly as a
// different user (a job container runs as root), and chmod on a file owned
// by another user fails with EPERM.
if (osType !== "win") {
const binaryPath = path.join(toolPath, binaryName);
await exec.exec("chmod", ["+x", binaryPath]);
}
}

core.addPath(toolPath);

if (osType !== "win") {
const binaryPath = path.join(toolPath, binaryName);
await exec.exec("chmod", ["+x", binaryPath]);
}
}

export function getSourceMetadata(jobId?: string) {
Expand Down