-
Notifications
You must be signed in to change notification settings - Fork 28
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
Highline deprecation warnings make appliance_console difficult to use #231
Comments
I thought we upgraded to highline 2.1.0? #201 |
Oh maybe that bump just hasn't made it to a release yet |
We have a ton of changes on master, but 8.0 was only released October 21, 2022. I know we had started to go to switching to 8.0, but then backed out of the kafka changes. However, when we enabled kafka I thought we'd have released another 8.0. Note that 7.2.2 was released on June 30, 2023. 8.0 on master: https://github.com/ManageIQ/manageiq/blob/f479740793cdd30108c84943564c9a1a4f710d03/Gemfile#L285 It feels like we missed something? @nasark @bdunne @jrafanie ? |
@Fryguy It looks like another 8.0 was not released https://github.com/ManageIQ/manageiq-appliance_console/tree/v8.0.0, but we switched the Gemfile in core to start using it. We're essentially using a version of appliance console from Oct 2022...? |
yeah, I thought we manually backported things on 7.2 branch because the kafka on 8.0 was giving us problems when kafka was removed from the release. Maybe we should review the changes and decide what we want to do. I can see bringing more back to 7.2 if we're not ready for the 8.0 changes or we can just do it and go with 8.0. |
We're already on 8.0 on master and quinteros, so im not sure why we haven't cut newer versions |
I released v8.1.0 with the changes from master. @agrare If you're still seeing this issue, please reopen. |
Confirmed this is fixed with appliance_console v8.1.0 |
Highline 1.6.21 with ruby 3.1 prints a number of deprecation warnings to the screen which causes the console to be difficult to use
The text was updated successfully, but these errors were encountered: