Michaela, first thank you for the response.
However, many of us have dozens, or hundreds (possibly thousands) of scenarios across many accounts (for partners) that require updating.
The biggest headache for customers is likely going to be the Execute GraphQL Query modules where we have to create and debug new queries. Most of the rest of the modules may just “work” once your team is done - assuming they make the effort to conform behaviors to match existing modules (which should be possible, nothing is changing in data structures).
We need a version of Execute GraphQL Query which provides an advanced field for us to manually specify an API version. As someone who has created make modules before, this adjustment from your dev team will take only minutes to create and test on its own.
This will afford all of your partners time adapt queries across their supported customers.
Worse is it sounds like this new version of the monday.com app is not a simply in-place update of the existing modules but an all new set of modules. This will be devastating to your customers because many have been dependent on partners to create complex scenarios for them - who are going to now have to rebuild every scenario for dozens of customers! There may be insufficient resources to complete this level of work.
I do not believe there is ANY need to release the make modules for the new API version separately, almost everything that is changing can be adapted seamlessly within the modules code to result in identical outputs and behaviors. The exceptions are a handful of column types no longer return values as they once did (but you can work around this easily), and a few column type identifiers may have changed in some circumstances (these could probably be rewritten on output to stay the same as old version for transition purposes to preserve any routing logic, with an advanced toggle to turn this on/off.)
However, we needed the ability to start adapting the custom queries in Execute GraphQL Query modules on October 1st to be able to service the needs of mutual customers. Please encourage the devs to put an advanced field on this single module in the existing version to allow us to specify the API version so we can at least start this work immediately. Then, if/when there is a new app version we’re in copy paste mode, not having to rewrite and debug queries mode - with only a matter of days to do it instead of three of months.
I know this single change can be completed quickly, and have zero impact on existing scenarios and usage of this module. A single mappable parameter that is used for the api-version header. If its not set, you exclude that header from the http request. If it is set, you send it.