Patching Previous App Versions on Forge

Forge
,
1

Hi everyone,

Back in March, we informed you about our ongoing efforts to enable the updating of previous app versions for maintenance and platform changes.

Understanding the challenges that arise with API and platform alterations, I am delighted to announce a new version of the CLI along with this guide detailing the process of updating previous app versions.

Now, when our platform changes, it is possible to upgrade any past app version, so long as the permission and egress rules remain the same between minor versions.

We have additional plans in store to address further development lifecycle challenges on Forge, and we eagerly anticipate sharing them with you in the near future.

Thanks,
Jemma Swaak

ECO-Testing Guide for Partners-230724-051523.pdf (224.7 KB)

7 Likes
2

This would be very helpful on Connect too, what are the plans for bringing the change there?

3

Hi @jasonboileau , Could you please provide more information on how this is applicable to Connect?

4

Just like Fuse, I’m assuming. As is, if I have a 1.0.0 and a 1.1.0 in the wild, I currently have no way to make changes to the 1.0.* branch of the app, even if there are 100s of customers still using those versions. As soon as 1.1.0 is released, the app descriptor for 1.0.* is forever locked in its current state.

5

Thanks for explaining @jasonboileau. We are only working on a Forge solution at this time, but I’ve passed on your feedback.