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

Make version warnings more robust #957

Merged
merged 1 commit into from
Mar 5, 2020

Conversation

schneems
Copy link
Contributor

@schneems schneems commented Mar 5, 2020

Users are mistakenly getting this warning when building apps:

       Your Ruby version is not present on the next stack
       You are currently using ruby-2.6.5 on heroku-16 stack.
       This version does not exist on heroku-18. In order to upgrade your stack you will
       need to upgrade to a supported Ruby version.
       For a list of supported Ruby versions see:
         https://devcenter.heroku.com/articles/ruby-support#supported-runtimes
       For a list of the oldest Ruby versions present on a given stack see:
         https://devcenter.heroku.com/articles/ruby-support#oldest-available-runtimes

I believe this is a result of network glitches. We should be cautious about warning about issues that don't actually exist.

@schneems schneems force-pushed the schneems/less-agressive-warning branch 3 times, most recently from 6517b40 to f59eac1 Compare March 5, 2020 16:57
Users are mistakenly getting this warning when building apps:

```
Your Ruby version is not present on the next stack
       You are currently using ruby-2.6.5 on heroku-16 stack.
       This version does not exist on heroku-18. In order to upgrade your stack you will
       need to upgrade to a supported Ruby version.
       For a list of supported Ruby versions see:
         https://devcenter.heroku.com/articles/ruby-support#supported-runtimes
       For a list of the oldest Ruby versions present on a given stack see:
         https://devcenter.heroku.com/articles/ruby-support#oldest-available-runtimes
```

I believe this is a result of network glitches. We should be cautious about warning about issues that don't actually exist.
@schneems schneems force-pushed the schneems/less-agressive-warning branch from f59eac1 to 5017ce0 Compare March 5, 2020 17:14
@schneems schneems merged commit da3fdae into master Mar 5, 2020
@schneems schneems deleted the schneems/less-agressive-warning branch March 5, 2020 18:18
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