I have noticed that once a ticket for a Dependency Update Request gets fixed the report on the dependency is not done again, even if there is a new version.
For example BEAM-4905 was fixed to the suggested dependency (2.0.5). However the latest version of the library is 2.1.2, and the ticket was not updated (and re-opened) or re-created for the newer version of the dependency.
Also BEAM-4904 required version 2.1.1 but the current version of the dependency is 2.2.0 and this was also not updated automatically.
Finally there is not any reference to both versions of the dependencies in the weekly Beam Dependency Check Report email.
Imported from Jira BEAM-6524. Original Jira may contain additional context.
Reported by: iemejia.
I have noticed that once a ticket for a Dependency Update Request gets fixed the report on the dependency is not done again, even if there is a new version.
For example BEAM-4905 was fixed to the suggested dependency (2.0.5). However the latest version of the library is 2.1.2, and the ticket was not updated (and re-opened) or re-created for the newer version of the dependency.
Also BEAM-4904 required version 2.1.1 but the current version of the dependency is 2.2.0 and this was also not updated automatically.
Finally there is not any reference to both versions of the dependencies in the weekly Beam Dependency Check Report email.
Imported from Jira BEAM-6524. Original Jira may contain additional context.
Reported by: iemejia.