-
Notifications
You must be signed in to change notification settings - Fork 57
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
Brew issues #563
Comments
@bmicklea Regarding the first issue: The kitops.rb file is automatically generated by the KitOps build process. Since we (Jozu) haven't built KitOps since before I added the brew install functionality, the kitops.rb file hasn't been updated. When we (Jozu) do build the next version of KitOps, the urls in the kitops.rb file should point to jozu-ai and not brett-hodges. |
@gorkem can we cut a KitOps release today? We've moved Brew into our KitOps docs so I'd like to make sure everything works as expected (it worked for me). |
So a new Kit release was cut last week (https://github.com/jozu-ai/kitops/releases/tag/v0.3.4), but the Are you sure it auto-updates when a new Kit version is built? Did a step fail or skip last week? |
There was an issue with the way I was setting an environment variable in the Github Action that builds the .rb file. I made the change last week. @amisevsk Can we push a new release of Kitops to enable the Homebrew installation? |
I believe we're waiting on a couple of PRs to be merged before cutting a new minor release |
Can you add links to those so we can stay on top of getting the release cut? |
Nice - that will be an impactful release:
I wouldn't hold the release for (4) but it would make a nice addition. |
Closing this issue as the Homebrew bug is fixed as of KitOps v.0.4.0 and a separate Issue has been opened related to creating a Homebrew Cask (See the Issue Description above.) |
Describe the bug
There are some issues with the
kitops.rb
file in our brew install:brett-hodges
organization for the download (should pull from main kitops)The text was updated successfully, but these errors were encountered: