Skip to content

Breaking change to Git Credential API #10034

@eddymoulton

Description

@eddymoulton

Severity

No response

Version

2026.2.10828

Latest Version

None

What happened?

Some clients may fail to make requests to the create/modify Git credential endpoints due to a new required field Details.Type being added.

Making changes through the UI is still fully functional

Reproduction

Create/modify a git credential directly from the API or with a client that does not already support the Details.Type field.

Example payload

{
    "SpaceId":"",
    "Name":"sample",
    "Description":"",
    "Details": {
        "Username":"user",
        "Password": { "HasValue":true, "NewValue":"test" }
    },
    "RepositoryRestrictions": { "Enabled":false, "AllowedRepositories":[] }
}

Error:

{
  "ErrorMessage": "There was a problem with your request.",
  "Errors": [
    "The Type field is required."
  ],
  "Details": {
    "Details.Type": "The Type field is required."
  }
}

Error and Stacktrace

More Information

No response

Workaround

If you have access to change the request payload, merging in the following to your requests will get around the error.

"Details: {
    "Type": "UsernamePassword"
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugThis issue represents a verified problem we are committed to solving

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions