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
When I deprecate packages and click save the UI tells me "Your packages have been undeprecated. It may take several hours for this change to propagate through our system." which is the opposite of what I was doing, so now I don't know if they're going to be deprecated or not.
Repro Steps
Pick a package where you want to deprecate old versions.
Select the versions.
Click save
See text at top of screen
Expected Behavior
The UI tells me
"Your packages have been deprecated. It may take several hours for this change to propagate through our system."
Screenshots
No response
Additional Context and logs
No response
The text was updated successfully, but these errors were encountered:
It looks like our UI is not very intuitive. We need to clarify what is going on or improve the UI to be more specific.
When the first time comes to deprecate the menu, it looks like this. Pressing save technically does nothing unless the previous package was deprecated. We need to warn about it.
If I tick the checkbox, then it deprecates the package.
But if I uncheck it, then it un-deprecates the package, now message looks bit different.
Impact
It bothers me. A fix would be nice
Describe the bug
When I deprecate packages and click save the UI tells me "Your packages have been undeprecated. It may take several hours for this change to propagate through our system." which is the opposite of what I was doing, so now I don't know if they're going to be deprecated or not.
Repro Steps
Pick a package where you want to deprecate old versions.
Select the versions.
Click save
See text at top of screen
Expected Behavior
The UI tells me
"Your packages have been deprecated. It may take several hours for this change to propagate through our system."
Screenshots
No response
Additional Context and logs
No response
The text was updated successfully, but these errors were encountered: