Thanks a lot for your answer. You
Thanks a lot for your answer. You understood correctly my situation.
the 3 things you suggested sounds great but :
1. I can send an email to all the users using the Apify feature. But it won't ensure my users will follow it. I am quite afraid of the amount of support I am going to do
2. Correct me if I am wrong, but publishing a new version does not automatically update the users Actor builds, does it ? I mean If latest is 1.10 and I publish a new 1.9 (for instance 1.9.6) -> users that were using a build 1.9.5 will stay on 1.9.5 unless they manually update their version right ?
3. That is another solution as for support once I break their actor version. But it will not make the transition smooth...
I would love a way to avoid support
the 3 things you suggested sounds great but :
1. I can send an email to all the users using the Apify feature. But it won't ensure my users will follow it. I am quite afraid of the amount of support I am going to do
2. Correct me if I am wrong, but publishing a new version does not automatically update the users Actor builds, does it ? I mean If latest is 1.10 and I publish a new 1.9 (for instance 1.9.6) -> users that were using a build 1.9.5 will stay on 1.9.5 unless they manually update their version right ?
3. That is another solution as for support once I break their actor version. But it will not make the transition smooth...
I would love a way to avoid support
