dep: update libxml2 to v2.9.14 (main branch) #2526
Merged
Conversation
This file contains 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
2 tasks
flavorjones
force-pushed
the
2525-update-libxml-2_9_14-main
branch
from
ccfc287
to
5c984cf
Compare
flavorjones
added
upstream/libxml2
dependencies
flavorjones
force-pushed
the
2525-update-libxml-2_9_14-main
branch
2 times, most recently
from
baa6453
to
d122437
Compare
A few fixes, including ones by your truly, have made it upstream (but not yet in a release) and the tests' conditional logic is being updated. Closes #2468
flavorjones
force-pushed
the
2525-update-libxml-2_9_14-main
branch
from
d122437
to
3ed5bf2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What problem is this PR intended to solve?
Update libxml2 to v2.9.14 rom v2.9.13, see #2525
Also ensure that tests pass against upstream libxml2 (#2468).
Have you included adequate test coverage?
This PR updates tests to reflect the difference in how incorrectly-opened comments are handled in this release.
Does this change affect the behavior of either the C or the Java implementations?
The C native implementation handling of incorrectly-opened comments is different from previous and different from the JRuby implementation's handling. These differences are fully captured and explained in the test suite.