Request publish to Maven Central
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 30
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- This issue affects my Ory Network project.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Describe the bug
There are several fields that were behaving as non-nullable even though they were nullable. The details of this issue can be found in this discussion: https://github.com/ory/hydra/issues/3360.
Having looked at the source code currently in main, it appears as if this issue has been resolved. However, the code has not been published to Maven Central. This means the updates are unavailable to use and it requires implementing a work-around.
This issue is to request that we publish a new patch version of the Java SDK to Maven Central so the community can take advantage of the bug fix already that has already been merged.
Reproducing the bug
See: https://github.com/ory/hydra/issues/3360.
Relevant log output
No response
Relevant configuration
No response
Version
v2.0.2
On which operating system are you observing this issue?
None
In which environment are you deploying?
None
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current main branch and the fix discussed in ory/hydra#3360. Confirm which Java SDK patch version contains the nullable-field fix and inspect the repository's release configuration and contribution guidance. Done means that a new patch version is published and available from Maven Central.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100