Repository navigation
Rebase version scheme: drop inherited MAJOR (4.x.x -> 0.x.x) - #5
Merged
Merged
Conversation
The major version 4 was inherited from the original solis_modbus fork and doesn't reflect SolisConnect's own release history. Reset MAJOR to 0 (keeping MINOR/PATCH as-is: 4.1.5 -> 0.1.5). Tags/release for v4.1.5 are replaced with v0.1.5 as a follow-up to this merge. This branch is intentionally not named patch/dev so the auto-release workflow treats this as a no-op merge; the tag/release swap is done manually afterward. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
Failed to generate code suggestions for PR |
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.
Summary
manifest.jsonversion4.1.5->0.1.5. The4major version was inherited from the originalsolis_modbusfork and doesn't reflect SolisConnect's own release history; resetting MAJOR to0while keeping MINOR/PATCH as-is.v4.1.5tag/release will be deleted and replaced withv0.1.5manually once this merges (not by the auto-release workflow, since this branch isn'tpatch/dev, so that workflow correctly no-ops here).Test plan
🤖 Generated with Claude Code