Bump mittwald/api-client from 2.1.87 to 2.1.91

[dependabot]

Bumps mittwald/api-client from 2.1.87 to 2.1.91.

Release notes

Sourced from mittwald/api-client's releases.

v2.1.91

Added

• Introduced a new property cronjobId to the CronjobExecution class, allowing the association of a unique identifier for each cron job execution.
• Updated the constructor of the CronjobExecution class to accept cronjobId as a parameter.
• Added a getter method getCronjobId() to retrieve the cronjobId.
• Implemented a method withCronjobId() to enable fluent updates of cronjobId while validating the input.
• Adjusted serialization and deserialization methods to include the cronjobId in the output and input processing.

v2.1.90

Added Features

New API Request and Response Handling for Listing Own Extensions

• Implemented an API client for fetching a contributor's extensions including:
  • ExtensionListOwnExtensionsRequest: Request object for listing the contributor's extensions with parameters for pagination and limits.
  • ExtensionListOwnExtensionsOKResponse: Successful response containing an array of OwnExtension objects.
  • ExtensionListOwnExtensionsDefaultResponse: Response object for handling general errors.
  • ExtensionListOwnExtensionsTooManyRequestsResponse: Response handling for rate-limiting errors.
  • ExtensionListOwnExtensionsTooManyRequestsResponseBody: Body structure for the too-many-requests response.

Schema Definitions

• Added OwnExtension schema which details the properties and structure of an extension, along with its associated models.
• Defined OwnExtensionState enumeration to manage extension states.

Client Changes

• Updated MarketplaceClient interface and its implementation to include a method for listing the contributor's extensions:
  • Added extensionListOwnExtensions method in MarketplaceClient.
  • Implemented the same in MarketplaceClientImpl, with error handling for various response scenarios.

These additions enhance the functionality of the API client, allowing users to manage and retrieve details about their specific extensions efficiently.

v2.1.89

Added

• Introduced a new schema for ServiceRequest, providing a structured way to handle service requests within the application.
• Added a new enumeration ServiceRequestMessageContent to define potential message content types.
• Implemented a new class ServiceRequestRelocationPayload that encapsulates the payload required for handling service requests related to relocations, including detailed contact and domain information.
• Included classes for managing relocation payload components: ServiceRequestRelocationPayloadContact, ServiceRequestRelocationPayloadDomain, ServiceRequestRelocationPayloadSource, and ServiceRequestRelocationPayloadTarget to facilitate structured data handling.

Changed

• Renamed the case from project_email_admin to projectemailadmin in the NotificationRole enumeration.
• Updated the ServiceRequestRelocationPayloadTargetPricesItem class from its previous representation as DepartmentWithStatus to support pricing information directly associated with service requests, with elements such as name and price.

Other Changes

• Added validation and conversion methods to the newly created classes to ensure data integrity and ease of use throughout the application.
• Introduced the ServiceRequestType enum for defining request types, specifically accommodating service request categorizations like 'SERVICE_REQUEST'.

v2.1.88

Added

• Extension Instance Retrieval for Customer
  • Implemented functionality to retrieve the specific extension instance for a customer. This includes:

... (truncated)

Commits

• 04aee49 feat: add cronjobId property to CronjobExecution schema and modify related me...
• ed3a463 feat(marketplace): add method to list own extensions of contributor in Market...
• 4992e70 feat: remove DepartmentWithStatus class and update NotificationRole case nami...
• 20b2fec feat: add verification endpoints and extend marketplace functionality
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #225.