Skip to content

fix(release): handle empty manifest for first release auto-merge #191

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
fiunchinho merged 1 commit into from
Jun 1, 2026
Merged

fix(release): handle empty manifest for first release auto-merge #191

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
5 changes: 4 additions & 1 deletion .github/workflows/release.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,9 +105,12 @@ jobs:
base_branch=$(jq -r '.baseBranchName' <<<"$PR_JSON")

# Read the single root (".") entry of the release-please manifest at a ref.
# On a fresh repo the manifest is an empty object until the first release lands,
# so a missing "." key is normalized to 0.0.0 — otherwise the numeric comparisons
# below silently fall through and the first release's bump is classified as none.
manifest_version() {
gh api "repos/${GH_REPO}/contents/.release-please-manifest.json?ref=$1" \
-H "Accept: application/vnd.github.raw" | jq -r '.["."]'
-H "Accept: application/vnd.github.raw" | jq -r '.["."] // "0.0.0"'
}

current=$(manifest_version "$base_branch")
Expand Down