You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current Homebrew release has no built-in way to specify a previous release. The current v2.1.1 breaks our usage pattern for my entire org, and there is no straightforward way for users to downgrade.
A few stable releases should be published to Homebrew to allow for downgrading in these scenarios.
The text was updated successfully, but these errors were encountered:
hi @joshgch down grading to which version? If it's one of the v1.x.x versions we won't do that, we aren't supporting v1 releases. Also, can you point me at docs on homebrew downgrading? Is there something more to it than targeting a version at install? e.g. brew install okta-aws-cli@2.0.0
I have seen it with other packages, but don't know the technical details of how it's achieved. Node is one example where several versions are available.
As you mentioned, it would just be referenced with @ 2.0.0. No need to downgrade to v1, we just need a way to back out of the latest update for cases like today where a change broke our usage pattern.
The current Homebrew release has no built-in way to specify a previous release. The current v2.1.1 breaks our usage pattern for my entire org, and there is no straightforward way for users to downgrade.
A few stable releases should be published to Homebrew to allow for downgrading in these scenarios.
The text was updated successfully, but these errors were encountered: