Skip to content

Conversation

melissalinkert
Copy link
Member

This tries to handle the cases where the result of the upgrade check is non-empty string indicating that something went wrong.

The original issue that prompted this change was a Too many hits ... response from the registry, which was incorrectly interpreted as a new version being available.

Effectively untested, thus the draft status. We likely need to coordinate some time to test this together with the current state of the registry, to make sure both pieces are actually working together as intended.

cc @jburel @chris-allan

…response code

This tries to handle the cases where the result of the upgrade check is non-empty
string indicating that something went wrong.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants