chore: bump @mittwald/api-client from 4.430.0 to 4.433.0 in the mittwald-api group across 1 directory - #2055
Open
dependabot[bot] wants to merge 2 commits into
Open
Conversation
Bumps the mittwald-api group with 1 update in the / directory: [@mittwald/api-client](https://github.com/mittwald/api-client-js). Updates `@mittwald/api-client` from 4.430.0 to 4.433.0 - [Release notes](https://github.com/mittwald/api-client-js/releases) - [Changelog](https://github.com/mittwald/api-client-js/blob/master/CHANGELOG.md) - [Commits](mittwald/api-client-js@4.430.0...4.433.0) --- updated-dependencies: - dependency-name: "@mittwald/api-client" dependency-version: 4.433.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: mittwald-api ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/mittwald-api-06af863685
branch
from
August 4, 2026 20:23
4061374 to
093021a
Compare
The mStudio OpenAPI spec marks `app-link-database` and `app-replace-database` as deprecated, so `@mittwald/api-client` stopped generating client methods for them in 4.431.0. This broke compilation of the `app database link` and `app database replace` commands. Both endpoints are still served by the API and have no successor operations, so invoke them through the client's Axios instance instead of dropping the commands. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
gandie
requested changes
Aug 6, 2026
gandie
left a comment
Member
There was a problem hiding this comment.
This introduces future issues. Better way exists afaik.
| databasePurposeFlag, | ||
| } from "../../../lib/resources/app/database/flags.js"; | ||
| import { resolveDatabaseId } from "../../../lib/resources/app/database/lookup.js"; | ||
| import { linkDatabase } from "../../../lib/resources/app/database/deprecated_operations.js"; |
Member
There was a problem hiding this comment.
No. Code agent forgot to update api-client and did not find actual operation that replaces the old one.
If it did, it would have seen that a perfectly fine alternative exists and provides the fields needed, at least specs say so. Signature in older api clients did not contain database fields yet.
Member
There was a problem hiding this comment.
Full ack, this is NOT a good solution. 🙅♂️
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the mittwald-api group with 1 update in the / directory: @mittwald/api-client.
Updates
@mittwald/api-clientfrom 4.430.0 to 4.433.0Release notes
Sourced from @mittwald/api-client's releases.
Changelog
Sourced from @mittwald/api-client's changelog.
Commits
ef09e5echore(release): bump version to 4.433.065a3485feat: update generated clientfe4dcabchore(release): bump version to 4.432.09e6e495feat: update generated client75f76cechore(release): bump version to 4.431.02be8e78feat: update generated client