search

mittwald / deployer-recipes

Collection of deployer recipes for interacting with the mittwald cloud platform
MIT License
3 stars 0 forks source link

Bump mittwald/api-client from 2.1.44 to 2.1.49 #170

Closed dependabot[bot] closed 3 weeks ago

dependabot[bot] commented 3 weeks ago

Bumps mittwald/api-client from 2.1.44 to 2.1.49.

Release notes

Sourced from mittwald/api-client's releases.

v2.1.49

Features

  • Enhanced Customer Management: Added a new mechanism to handle bad requests in the customer listing functionality, improving error handling.
  • Multi-Factor Authentication (MFA) Support: Integrated MFA attributes into the user schemas, including fields for active and setup states, to enhance user security management.
  • Password Update Tracking: Introduced a new field to track when the user's password was last updated.

Improvements

  • ListCustomersRequest Enhancements: Added a search parameter to ListCustomersRequest, allowing for filtered customer searches. The input validation has also been refined to ensure robust data handling.
  • Structured Error Responses: The ListCustomersBadRequestResponse class has been implemented to provide clearer error messages when bad requests occur, streamlining client-side error management.
  • Unified MFA Handling: Introduced UserMfa and UserInternalMfa classes to encapsulate MFA-related data accurately, ensuring consistent management across different user contexts.

Bug Fixes

  • Improved error handling in CustomerClientImpl by implementing a case for 400 response codes to ensure that users receive appropriate feedback during bad requests.

v2.1.48

Features

  • Enhanced Pagination and Limit Control: Introduced limit, skip, and page properties to the NotificationsListNotificationsRequest class to provide better control over the number of notifications returned and pagination support.

New Properties

  • limit: An integer property with a default value of 500 and a minimum value of 1, specifying the maximum number of notifications to return.
  • skip: An integer property with a default value of 0, indicating the number of notifications to skip for pagination.
  • page: An optional integer property allowing users to specify the page number for paginated results.

Updated Methods

  • Constructor: Now requires limit and skip parameters upon instantiation.
  • getLimit(): Added method to retrieve the limit value.
  • getSkip(): Added method to retrieve the skip value.
  • getPage(): Added method to retrieve the page value.
  • withLimit(): Allows setting the limit with validation.
  • withSkip(): Allows setting the skip value with validation.
  • withPage(): Allows setting the page value with validation.
  • withoutPage(): Provides a method to unset the page.

Updated Serialization and Deserialization

  • The serialization and deserialization methods have been updated to accommodate the new properties, ensuring they are properly handled when creating instances from input arrays and converting instances to output arrays.

v2.1.47

Features Added

  • Simplification of various request classes by removing unnecessary complexity related to user ID types. The user ID is now uniformly treated as a string, simplifying the method signatures and internal behavior of the requests.

Changes

  • AddPhoneNumberRequest:
    • Removed the complex type definition for userId, simplifying it to a string type.

... (truncated)

Commits
  • 09ba95e feat: add search parameter to ListCustomersRequest and extend User schema wit...
  • 6c2ed71 feat: add pagination parameters to NotificationsListNotificationsRequest
  • 0d9476e refactor: simplify user ID handling and remove unnecessary alternatives
  • cf92026 feat: add frontendFragments property and methods to Extension schema
  • 762d200 feat: add pagination parameters to ListProjectsRequest and ListServersRequest
  • See full diff in compare view


Dependabot compatibility score

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 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[bot] commented 3 weeks ago

Superseded by #171.