Skip to content

5.6.0 includes a breaking change in the API #1155

@MarkEWaite

Description

@MarkEWaite

I believe that the API change of the fourth argument boolean (primitive type, nulls not allowed) to Boolean (object, nulls allowed) is a breaking change in pull request:

The change in the diff went from this:

    public ProjectHook addHook(Object projectIdOrPath, String url, ProjectHook enabledHooks,
            boolean enableSslVerification, String secretToken) throws GitLabApiException {

to this:

    public ProjectHook addHook(Object projectIdOrPath, String url, ProjectHook enabledHooks,
            Boolean enableSslVerification, String secretToken) throws GitLabApiException {

The Jenkins issue tracker received two reports of method not found exceptions in issue JENKINS-73672.

Is there a critical need for the change of type in the argument?

If not, could that change be reverted and a new release provided so that API compatibility is retained?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions