You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our securities tab, we have several updates that have come in for packages we use. Given these are security updates it's important that we keep our application healthy by updating these in a timely manner.
Some of these updates are for the same package, only the most recent upgrade needs to be applied. For instance there are several django updates that call out updating to 4.2.14 and then later ones mention 4.2.15. There would be no point in upgrading to 4.2.14 and then updating to 4.2.15 and running the dependency updates twice; just update to the most recent one (4.2.15 in this case)
Acceptance criteria
all security updates are applied to our code base
if an update has already been applied to our system and is now non-applicable/ already resolved, just dismiss the alert as "inaccurate"
Additional context
No response
Links to other issues
No response
The text was updated successfully, but these errors were encountered:
Issue description
In our securities tab, we have several updates that have come in for packages we use. Given these are security updates it's important that we keep our application healthy by updating these in a timely manner.
Some of these updates are for the same package, only the most recent upgrade needs to be applied. For instance there are several django updates that call out updating to 4.2.14 and then later ones mention 4.2.15. There would be no point in upgrading to 4.2.14 and then updating to 4.2.15 and running the dependency updates twice; just update to the most recent one (4.2.15 in this case)
Acceptance criteria
Additional context
No response
Links to other issues
No response
The text was updated successfully, but these errors were encountered: