Do I need to update jsf injection jars every time I migrate to new EAP version?

I am not sure if this is the bug or not, but would like to discuss it. Here is my concern.

When migrating myfaces 2.2.12 jsf application from 7.3.5 (OK) -> 7.3.7 (OK) -> 7.3.8 (ERROR) -> 7.4.0 (ERROR) I saw this error

Caused by: java.lang.IncompatibleClassChangeError: Found interface org.jboss.as.web.common.WebInjectionContainer, but class was expected

Seems to me this error is consequence of this fix [1]. To properly setup EAP one need to use current jsf injection jars as described in [2] and really after this step error is gone.

But my concern is; if user is configuring on OpenShift using cutom modules [3], does it mean now he needs update jars with each update to new eap version? Was it always like that?

My first assumption was [1] changed migrating from 7.3.7 to 7.3.8, but was not expecting same error when migrating from 7.3.8 to 7.4.0.

We are saying user should be able to migrate with existing application to new version without changing the application and this is somehow breaking it.
Also noticed that error couple of days ago in upstream [4]. So is this something users will face more frequently now? Could we do something to mitigate that error?

[1] https://github.com/jbossas/jboss-eap7/commit/265176866a72897ca7da2f48196f9cd74ef8ee43#diff-bb44d898af7bb5f81b47d3bd0d73ac1fa8396cbf975934251e45618459543b58L39
[2] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.3/html/configuration_guide/jakarta_server_faces_configuration#add_jsf_injection
[3] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.3/html-single/getting_started_with_jboss_eap_for_openshift_container_platform/index#custom_configuration
[4] https://groups.google.com/g/wildfly/c/MVXkXknrKMk/m/SuZnR3JSDQAJ https://stackoverflow.com/questions/68160568/upgraded-to-wildfly-24-0-0-final-deployed-ear-with-this-error