ci: drop the release-please component so merged release PRs get tagged - #156
Merged
Merged
Conversation
The release PR branch carries no component, so a configured `solpan` made release-please skip #143 after merge, leave it untagged, and abort every later run.
jamesarich
enabled auto-merge
September 23, 2026 12:44
Contributor
Code Coverage Report📊 Line Coverage: 12.61%
|
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.
The release PR branch carries no component, so the configured
solpanmakes release-please skip #143 after merge (PR component: undefined does not match configured component: solpan). It stays untagged and every later run aborts on it. With no component both sides normalise to empty and the next run tagsv1.1.0.