There are 7 comments.
 
 
XWiki Platform / cid:jira-generated-image-avatar-21205f17-02db-4f0e-87e2-f12e7cbbde56 XWIKI-9565 Open

Transitively-installed extension with upgrade available doesn't show up in the Extension Updater page

 
View issue   ·   Add comment
 

7 comments

 
cid:jira-generated-image-avatar-fbc6e58f-60ca-4f5a-8f96-fb36625fdf9b Thomas Mortagne on 16/Nov/26 14:14
 

but is the risk of breaking dependent extensions still comparable to what it was when this issue was filed 13 years ago?

Definitely.

This makes it difficult to identify and apply security fixes for dependencies.

Depending on a vulnerable version is a very bad idea, it's not the job of the upgrade check to fix that.

 
cid:jira-generated-image-avatar-fbc6e58f-60ca-4f5a-8f96-fb36625fdf9b Thomas Mortagne on 16/Nov/26 14:15
 
bq. but is the risk of breaking dependent extensions still comparable to what it was when this issue was filed 13 years ago?

Definitely.

bq.
This makes Upgrade a parent extension does not necessarily upgrade a dependency. The dependency may stay at its current version if it difficult to identify and apply security fixes for dependencies satisfies the parent’s declared version constraint .

Depending on a vulnerable version is a very bad idea, it's not the job of the upgrade check to fix that.
 
cid:jira-generated-image-avatar-fbc6e58f-60ca-4f5a-8f96-fb36625fdf9b Thomas Mortagne on 16/Nov/26 14:15
 
bq. but is the risk of breaking dependent extensions still comparable to what it was when this issue was filed 13 years ago?

Definitely.

bq. 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.

Depending on a vulnerable version is a very bad idea, it's not the job of the upgrade check to fix that.
 
cid:jira-generated-image-avatar-fbc6e58f-60ca-4f5a-8f96-fb36625fdf9b Thomas Mortagne on 16/Nov/26 14:17
 
bq. is the risk of breaking dependent extensions still comparable to what it was when this issue was filed 13 years ago?

Definitely.

bq. 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.

Depending on a vulnerable version is a very bad idea, it's not the job of the upgrade check to fix that.


Note that the specific use case of security vulbnerability is supposed to be covered by the vulnerability the Security Vulnerabilities application (which is supposed to suggest upgrade and lead to version to upgrade to), but its UI still need a bit more work.
 
cid:jira-generated-image-avatar-fbc6e58f-60ca-4f5a-8f96-fb36625fdf9b Thomas Mortagne on 16/Nov/26 14:17
 
bq. is the risk of breaking dependent extensions still comparable to what it was when this issue was filed 13 years ago?

Definitely.

bq. 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.

Depending on a vulnerable version is a very bad idea, it's not the job of the upgrade check to fix that.

Note that the specific use case of security vulbnerability is supposed to be covered by the
vulnerability the Security Vulnerabilities application (which is supposed to suggest upgrade and lead to version to upgrade to), but its UI still need a bit more work.
 
cid:jira-generated-image-avatar-fbc6e58f-60ca-4f5a-8f96-fb36625fdf9b Thomas Mortagne on 16/Nov/26 14:18
 
bq. is the risk of breaking dependent extensions still comparable to what it was when this issue was filed 13 years ago?

Definitely.

bq. 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.

Depending on a vulnerable version is a very bad idea, it's not the job of the upgrade check to fix that.

Note that the specific use case of security vulbnerability is supposed to be covered by the
[ Security Vulnerabilities |https://extensions.xwiki.org/xwiki/bin/view/Extension/Extension/Security/] application (which is supposed to suggest upgrade and lead to version to upgrade to), but its UI still need a bit more work.
 
cid:jira-generated-image-avatar-fbc6e58f-60ca-4f5a-8f96-fb36625fdf9b Thomas Mortagne on 16/Nov/26 14:19
 
bq. is the risk of breaking dependent extensions still comparable to what it was when this issue was filed 13 years ago?

Definitely.

bq. 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.

Depending on a vulnerable version is a very bad idea, it's not the job of the upgrade check to fix that.

Note that the specific use case of security vulbnerability is supposed to be covered by the [Security Vulnerabilities|https://extensions.xwiki.org/xwiki/bin/view/Extension/Extension/Security/
UI/ ] application (which is supposed to suggest upgrade and lead to version to upgrade to), but its UI still need a bit more work.