Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List updated programs / components post upgrade in a bullet point list #943

Open
ylluminate opened this issue Oct 13, 2024 · 1 comment
Open
Labels
C-feature request New feature request

Comments

@ylluminate
Copy link

I'm finding that topgrade is extremely useful, but it's a bit easy to miss some things that are updated that are important. Having a final bullet point list of things that have been upgraded post upgrade would be extremely helpful to see so as to note if something critical has been updated that needs attention.

An example of this is when the awesome eloston-chromium is updated and your browser tabs will start dying inexplicably unless you close and reopen the browser. Other similar tools and browsers behave in this fashion where they need to be quit and restarted and without an easy to reference list it's very likely one will not look closely enough and get caught up for a brief period wondering why things are blowing up around them...

@ylluminate ylluminate added the C-feature request New feature request label Oct 13, 2024
@ylluminate ylluminate changed the title List updated components post upgrade in a bullet point list List updated programs / components post upgrade in a bullet point list Oct 13, 2024
@SteveLauC
Copy link
Member

An example of this is when the awesome eloston-chromium is updated and your browser tabs will start dying inexplicably unless you close and reopen the browser.

True, I encountered this multiple times.

Having a final bullet point list of things that have been upgraded post upgrade would be extremely helpful

I understand this feature will be useful, But I guess it is not easy to implement as it requires Topgrade to parse the output of the commands, extract the updated packages, and collect them. Unless the underlying tools support structured output (e.g., JSON), I am afraid it will be hard to implement and almost impossible to maintain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature request New feature request
Projects
None yet
Development

No branches or pull requests

2 participants