Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
4465247 to
84f2329
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #327 +/- ##
=======================================
Coverage 63.64% 63.64%
=======================================
Files 38 38
Lines 1400 1400
=======================================
Hits 891 891
Misses 447 447
Partials 62 62 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
84f2329 to
6159fb4
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
6159fb4 to
67657cc
Compare
ar3s3ru
added a commit
that referenced
this pull request
Apr 21, 2026
## Summary Removes `package-name` from `release-please-config.json`. This field was triggering an upstream release-please bug that left merged release PRs stuck in `autorelease: pending` and prevented tag/GitHub-Release creation. ## Root cause With `include-component-in-tag: false` (as we have configured), release-please's PR-creation leg correctly uses an empty component. But its PR-parsing leg — used during `buildReleases` to decide whether to cut a tag — ignores that flag and falls through to `getBranchComponent()`, which returns the `package-name` value (\"go-eventually\"). The configured component (\"go-eventually\") is then compared against the component parsed from the branch name (\`release-please--branches--main\`), which is \`undefined\`. Mismatch → early return → no tag. This is the upstream bug tracked at [googleapis/release-please#2214](googleapis/release-please#2214), open since Feb 2024. ## Evidence from the stuck workflow run Run [#24731049954](https://github.com/get-eventually/go-eventually/actions/runs/24731049954) (post-merge of #327) logged: \`\`\` ⚠ PR component: undefined does not match configured component: go-eventually \`\`\` and then: \`\`\` ⚠ There are untagged, merged release PRs outstanding - aborting \`\`\` The tag `v0.4.0` was never created even though PR #327 was merged successfully. ## Fix Remove `package-name` — it provides no value here: - We don't use components in tags (`include-component-in-tag: false`). - There's no `version-file` to write the package name into. - The tag name is always the bare `vMAJOR.MINOR.PATCH` at repo root. With `package-name` gone, `getBranchComponent()` returns `''`, which matches the empty component parsed from the release branch name, and `buildReleases` no longer bails. ## Recovery for the stuck v0.4.0 The stalled `v0.4.0` tag will be created manually (separately from this PR) by tagging commit `5e41a02026adf5f4d585aa4b93b9a47bf3326c3f` and flipping PR #327's label from `autorelease: pending` → `autorelease: tagged`. After that, this config fix ensures the next release cycle (`v0.4.1` for this commit) tags automatically when its release PR is merged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.4.0
0.4.0 (2026-04-21)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.