Update dependency jaxen:jaxen to v2.0.1#26666
Conversation
There was a problem hiding this comment.
The release notes look much, much larger than a patch release and include many changes that were fixed by Copilot. This change needs much deeper review before it is merged into Jenkins core.
The library is used in Jelly and the EC2 plugin.
Some test ideas:
- Upgrade jaxen 2.0.0 to 2.0.1 in Jelly and test the incremental in Stapler, Jenkins core, plugin BOM
- Upgrade jaxen 2.0.0 to 2.0.1 in Jelly and test the incremental in ATH
- Upgrade jaxen 2.0.0 to 2.0.1 in EC2 plugin and test the incremental in plugin BOM and ATH (done with the earlier tests, since the jaxen dependency in EC2 plugin is provided by Jenkins core)
Relevant pull requests:
5f7895d to
5bed497
Compare
Refer to the changelog at: * https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.1 Proposed for inclusion in Jenkins core with pull request: * jenkinsci/jenkins#26666 It is unclear when dependabot did not propose this update. Update generated with `mvn versions:use-latest-releases` Testing done: * Tests pass locally Testing to be done: * Create an incremental build of Stapler that uses the incremental build from this change * Include that incremental build in a Jenkins core incremental build * Test the Jenkins core incremental build in the plugin BOM * Test the Jenkins core incremental build in the acceptance test harness
Refer to the jaxen changelog at: * https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.1 Jelly pull request: * jenkinsci/jelly#183 Proposed for inclusion in Jenkins core with pull request: * jenkinsci/jenkins#26666
Refer to the jaxen changelog at: * https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.1 Jelly pull request: * jenkinsci/jelly#183 Stapler pull request: * jenkinsci/stapler#761 Proposed for inclusion in Jenkins core with pull request: * jenkinsci#26666 Testing done: * Confirmed that quick-build passes * Rely on ci.jenkins.io for more tests and to generate an incremental Testing to be done: * Use the incremental in plugin BOM and in acceptance test harness
Refer to the jaxen changelog at: * https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.1 Jelly pull request: * jenkinsci/jelly#183 Stapler pull request: * jenkinsci/stapler#761 Proposed for inclusion in Jenkins core with pull request: * jenkinsci/jenkins#26666 This incremental build was generated from core pull request: * jenkinsci/jenkins#26673 Testing done: * Confirmed that forensics api tests passed locally on weekly line * Let ci.jenkins.io run the other weekly tests
Refer to the jaxen changelog at: * https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.1 Jelly pull request: * jenkinsci/jelly#183 Stapler pull request: * jenkinsci/stapler#761 Proposed for inclusion in Jenkins core with pull request: * jenkinsci/jenkins#26666 Incremental build from from Jenkins core pull request: * jenkinsci/jenkins#26673 Testing done: * Passes Jelly tests * Passes Stapler tests * Passes Jenkins core tests * Passes plugin BOM tests
|
Seems best to not include this in Jenkins core until a Jelly release is created that includes jaxen 2.0.1 and a Stapler release is created that includes the new Jelly release. |
Includes jaxen 2.0.1 as described in their changelog: * https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.1 Jaxen 2.0.1 is proposed for Jenkins core by pull request: * jenkinsci/jenkins#26666 Testing done: * Tested with plugin BOM in: * jenkinsci/bom#6680 * Tested with acceptance test harness in: * jenkinsci/acceptance-test-harness#2684 * Automated tests all pass on my computer
Includes jaxen 2.0.1 as described in their changelog: * https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.1 Jaxen 2.0.1 is proposed for Jenkins core by pull request: * jenkinsci/jenkins#26666 Testing done: * Tested with plugin BOM in: * jenkinsci/bom#6680 * Tested with acceptance test harness in: * jenkinsci/acceptance-test-harness#2684 * Automated tests all pass on my computer
MarkEWaite
left a comment
There was a problem hiding this comment.
This PR is now ready for merge. We will merge it after approximately 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process.
/label ready-for-merge
Needs to be merged along with pull requests:
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
This PR contains the following updates:
2.0.0→2.0.1Release Notes
jaxen-xpath/jaxen (jaxen:jaxen)
v2.0.1: 2.0.1Compare Source
The build is now fully byte-per-byte reproducible. If you use the same JDK on the same platform to compile, you'll get the same bytes out every time. This is a prerequisite for hash-based defenses against supply chain and MITM attacks.
The release has been mostly automated. It's not quite a one-click deploy but it's close.
Several bugs in XPath conformance detected by Claude Sonnet 4.6 were fixed:
round()function returns negative zero for values between -0.5 and -0.0.number()function rejects some strings Java recognizes as a number but XPath does not.anyMatchingNode()andevaluateAsBoolean()no longer throwNoSuchElementExceptionwhen evaluating an XPath expression with multiple predicates and more nodes than predicates.DefaultCommentNodeStep.getText()includes predicates. (This one's very unlikely to have any effect on XPath queries or evaluation.)The DOMNavigator can now search inside entity reference and document fragment nodes.
What's Changed
>by @Copilot in #257XPathReader.LTafter perf check by @Copilot in #275XXXnull-handling comment inAncestorOrSelfAxisIteratorby @Copilot in #276New Contributors
Full Changelog: jaxen-xpath/jaxen@v2.0.0...v2.0.1
Configuration
📅 Schedule: (UTC)
* 0-3 * * *)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.