fix: restore release for squashed PR #26 - #27
Merged
Conversation
Restore semantic-release detection for original PR #26 after it was squash-merged with a non-conventional subject. Written by Codex.
|
Merging this PR will release 2.2.5 (2026-07-21)Connector release changes
|
|
🎉 This PR is included in version 2.2.5 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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 code changes from #26 are already on
main, but the squash-generated merge subject was not recognized by semantic-release.This empty conventional commit restores the intended fix release signal without changing connector code.
Original PR: #26
Written by Codex.