Prep for 4.1.8 release #13053
Merged
Prep for 4.1.8 release #13053
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
v4.1.7 included a mistake in setting the shared library version number which caused link incompatibility between previous v4.1.x releases and 4.1.7. There isn't a great way to fix that, so this release undoes the age increment, which will mean that a 4.1.8 release is link compatible with 4.1.0 - 4.1.16, but not link compatible with 4.1.7. This seems better than any other path forward, given the low number of complaints about this issue since 4.1.7 was released 3 months ago. Signed-off-by: Brian Barrett <[email protected]>
|
Hello! The Git Commit Checker CI bot found a few problems with this PR: 16889ad: dist: Prep for v4.1.8 release
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
1 similar comment
|
Hello! The Git Commit Checker CI bot found a few problems with this PR: 16889ad: dist: Prep for v4.1.8 release
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
jsquyres
approved these changes
Jan 23, 2025
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.
v4.1.7 included a mistake in setting the shared library version number which caused link incompatibility between previous v4.1.x releases and 4.1.7. There isn't a great way to fix that, so this release undoes the age increment, which will mean that a 4.1.8 release is link compatible with 4.1.0 - 4.1.16, but not link compatible with 4.1.7. This seems better than any other path forward, given the low number of complaints about this issue since 4.1.7 was released 3 months ago.
bot:notacherrypick
Fixes #13052