Skip to content

Handle Pinget no-applicable upgrade result with zero exit code - #5244

Open
Wojciech Bigosinski (wojciech-bigosinski) wants to merge 1 commit into
Devolutions:mainfrom
wojciech-bigosinski:agent/pinget-no-applicable-upgrade
Open

Handle Pinget no-applicable upgrade result with zero exit code#5244
Wojciech Bigosinski (wojciech-bigosinski) wants to merge 1 commit into
Devolutions:mainfrom
wojciech-bigosinski:agent/pinget-no-applicable-upgrade

Conversation

@wojciech-bigosinski

Copy link
Copy Markdown
  • I have read the contributing guidelines, and I agree with the Code of Conduct.
  • Have you checked that there aren't other open pull requests for the same changes?
  • Have you tested that the committed code can be executed without errors?
  • Have you confirmed that this issue is caused by UniGetUI itself, and not by the package manager or the package involved?
    If the same issue can be reproduced outside UniGetUI with the relevant package manager or with the package itself, please report it there first. UniGetUI should only be used to track issues that are specific to UniGetUI's behavior or integration.

Pinget can return exit code 0 while printing No applicable upgrade found. UniGetUI previously treated this result as a successful upgrade.

This change recognizes Pinget's no-applicable output even when the exit code is 0 and routes it through UniGetUI's existing not-applicable upgrade handling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant