Skip to content

ci: set origin/HEAD before running release.sh - #168

Merged
eddietejeda merged 1 commit into
mainfrom
ci/release-origin-head
Oct 15, 2026
Merged

eddietejeda merged 1 commit into
mainfrom
ci/release-origin-head

Conversation

@eddietejeda

Copy link
Copy Markdown
Contributor

Same fix as sdk-python: the first Cut Release run there failed in release.sh prepare with fatal: empty string is not a valid pathspec because the script resolves the base branch from origin/HEAD, which actions/checkout never sets. Both jobs now run git remote set-head origin --auto before calling the script. No script change.

actions/checkout does not create refs/remotes/origin/HEAD, so
release.sh's default_branch() resolves to an empty string in CI, as the
first sdk-python Cut Release run showed.
@eddietejeda
eddietejeda requested a review from a team as a code owner October 15, 2026 19:38
@eddietejeda
eddietejeda requested review from shefeek-jinnah and removed request for a team October 15, 2026 19:38
@eddietejeda
eddietejeda enabled auto-merge (squash) October 15, 2026 19:38
@eddietejeda
eddietejeda merged commit 6e4f1f3 into main Oct 15, 2026
3 checks passed
@eddietejeda
eddietejeda deleted the ci/release-origin-head branch October 15, 2026 19:39
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.

1 participant