Skip to content

Fix Cut Release failing with Permission denied on release.sh - #4

Merged
fanis merged 1 commit into
masterfrom
claude/project-review-optimization-4xcgkm
Jul 3, 2026
Merged

Fix Cut Release failing with Permission denied on release.sh#4
fanis merged 1 commit into
masterfrom
claude/project-review-optimization-4xcgkm

Conversation

@fanis

@fanis fanis commented Jul 3, 2026

Copy link
Copy Markdown
Owner

The first Cut Release run failed with exit 126 (scripts/release.sh: Permission denied): the script was tracked in git without the executable bit (100644), which never mattered locally but fails when the Actions runner execs the path directly.

Two-line fix:

  • Track scripts/release.sh as executable (100755).
  • Invoke it as bash scripts/release.sh in the workflow, so a lost exec bit (e.g. from a Windows checkout) can never fail a release again.

After merging, re-run Actions → Cut Release.

scripts/release.sh was tracked without the executable bit, so the Actions
runner could not exec it directly. Set the bit and invoke it via bash in
the workflow so a lost bit can never fail a release again.
@fanis
fanis force-pushed the claude/project-review-optimization-4xcgkm branch from 5014e06 to dada351 Compare July 3, 2026 20:24
@fanis
fanis merged commit 24933ae into master Jul 3, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants