Extension upgrades are risky: breaking changes, missing migration guides & security gaps

[AravindhanV]

Writing this believe this will be a common issue across,

1. Breaking changes across version jumps

When upgrading an extension — especially when skipping several versions in between — there's no consolidated view of the breaking changes introduced. The only way to assess impact today is to review each intermediate version's release notes one by one, which isn't practical at scale.

2. Missing migration guidance

There doesn't appear to be a migration guide for these upgrades. In an enterprise org with tight change-management, this is a real gap — upgrades seem to require manual reconfiguration afterward, which risks configuration drift and errors.

3. Access control & security filters on extensions

We'd like user- and permission-based control on extensions to prevent accidental changes or removal and to strengthen our security posture — fine-grained control over who can modify or delete a given extension.

Using API to get the extension and its configuration to trigger the upgrade also has its obstacles

If any words or guidance would help

Thanks

[V_e]

Hi Aravindhan!

We are currently working on a solution to address concern 1 and 2.
With the goal that the Extension user is not exposed anymore to breaking changes between extension versions. This then also enables bigger version jumps without any work on your side.

We are currently figuring out the details, with the goal to deliver it in the next months.