Update jersey to v4 (major)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| org.glassfish.jersey.media:jersey-media-json-jackson (source) | dependencies | major | 3.1.11 -> 4.0.0 |
| org.glassfish.jersey.inject:jersey-hk2 (source) | dependencies | major | 3.1.11 -> 4.0.0 |
| org.glassfish.jersey.core:jersey-server (source) | dependencies | major | 3.1.11 -> 4.0.0 |
| org.glassfish.jersey.core:jersey-common (source) | dependencies | major | 3.1.11 -> 4.0.0 |
Release Notes
eclipse-ee4j/jersey (org.glassfish.jersey.media:jersey-media-json-jackson)
v4.0.0
Configuration
📅 Schedule: Branch creation - Every minute ( * * * * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 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 these updates again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot
Interesting - I didn't realize Jersey v4 was out.
The code itself here looks reasonable - everything compiles, our client codegen still looks good, and v2 APIs still work in practice in a bit of manual testing.
My only concern I guess is around the wisdom in upgrading to a X.0.0 release in general. They tend to be a bit buggier, so maybe we're better waiting for a 4.0.1, 4.1.0, etc? On the other hand, if this is only going to main, I imagine we'll see another version before 11 comes out anyways, so there's little actual risk here in practice.
A major version of a dependency (here, Jersey) is IMO ideally aligned with a major Solr version (10). Not mandatory but ideal. So lets!