Please confirm these before moving forward.
Describe the improvement
I am not certain if this is a regression or a feature request, since I don't know if you intended this UX or not. But it seems like an obvious UX omission.
I'm being initially terse with repro conditions, assuming this to be a base case. If not reproducible — then we might switch to the mountains of logs and all.
So the Installed Packages tab keeps its versions stale until refreshed. You can see the listed version still showing v0.5.3 after updating to v1.1.
Expectation: finishing an update procedure for a given package would trigger spot-update of Installed Packages metadata for the package in question.
Describe how this improvement could help users
Confusion.
Please confirm these before moving forward.
Describe the improvement
I am not certain if this is a regression or a feature request, since I don't know if you intended this UX or not. But it seems like an obvious UX omission.
I'm being initially terse with repro conditions, assuming this to be a base case. If not reproducible — then we might switch to the mountains of logs and all.
So the Installed Packages tab keeps its versions stale until refreshed. You can see the listed version still showing v0.5.3 after updating to v1.1.
Expectation: finishing an update procedure for a given package would trigger spot-update of Installed Packages metadata for the package in question.
Describe how this improvement could help users
Confusion.