Fix the version update for BC breaking changes #1965
Merged
Conversation
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
The refresh script was computing the level variable based on the kind of changes in the changelog of the unreleased version, and was later reinitializing the variable, losing that info.
stof
commented
Oct 25, 2025
| exit(1); | ||
| } | ||
| $parts = explode('.', $lastPackageVersion); | ||
| $level = 1; |
Member
Author
There was a problem hiding this comment.
this variable is initialized as 1 on line 242. Then, it is updated on line 246 to a value of 0 in case we have changes requiring a major version. But this was lost due to this line.
jderusse
approved these changes
Oct 25, 2025
Member
|
thank you @stof |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 refresh script was computing the level variable based on the kind of changes in the changelog of the unreleased version, and was later reinitializing the variable, losing that info.
This fixes the issue detected in #1964