Skip to content

fix: Update dependency versions to latest with Java migration to 17 - #83

Open
jmadhur87 wants to merge 6 commits into
masterfrom
mjain6/client-apiUpgrade
Open

jmadhur87 wants to merge 6 commits into
masterfrom
mjain6/client-apiUpgrade

Conversation

@jmadhur87

@jmadhur87 jmadhur87 commented Nov 2, 2026 •

Copy link
Copy Markdown

Upgrade Fortify Client API to 7.0.0.RELEASE and migrate to Java 17.
Update Jakarta SOAP and related dependencies.
Update GitHub Actions to use latest actions from Fortify shared actions.
Update JavaDoc

@jmadhur87 jmadhur87 self-assigned this Nov 2, 2026
@jmadhur87
jmadhur87 requested a review from rsenden November 2, 2026 08:41

@rsenden rsenden left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed:

  • Given that this repo lives in a separate organization (fortify-ps instead of fortify), and only uses GitHub-provided actions, no need to utilize fortify/shared-github
  • Not sure where the JavaDoc-related check failures/warnings come from, but ideally we should get rid of these, either by fixing the JavaDoc, or reconfiguring the pipeline to avoid JavaDoc issues from causing check failures
  • There seems to be a remaining CVE in fortify-client-api dependencies, so best to get that fixed first of necessary, and then update and release this repo accordingly

@jmadhur87
jmadhur87 requested a review from rsenden November 3, 2026 05:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants