[jira] [Commented] (BEAM-6524) Dependency Update Requests are not updated or created again if already fixed/closed

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-6524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174773#comment-17174773 ] 

Beam JIRA Bot commented on BEAM-6524:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Dependency Update Requests are not updated or created again if already fixed/closed
> -----------------------------------------------------------------------------------
>
>                 Key: BEAM-6524
>                 URL: https://issues.apache.org/jira/browse/BEAM-6524
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>            Reporter: Ismaël Mejía
>            Priority: P2
>              Labels: stale-P2
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)