I’d like to add a current use case to this ticket:
Check for updates does not show available updates for extensions installed as dependencies.
Search for an installed extension may not show the Upgrade option until its latest version is opened or selected manually.
Upgrade a parent extension does not necessarily upgrade a dependency. The dependency may stay at its current version if it satisfies the parent’s declared version constraint.
This makes it difficult to identify and apply security fixes for dependencies. For example, OIDC extension is installed as dependency in several cases, so their available security upgrades can be easy to miss.
The compatibility concern behind this behavior is understandable, but is the risk of breaking dependent extensions still comparable to what it was when this issue was filed 13 years ago? Has dependency metadata or upgrade planning evolved enough to assess this more safely? Could the updater offer an explicit check and reviewable upgrade plan for dependencies, showing their dependents and declared constraints, without upgrading them automatically?
Thanks, Camelia
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.