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
We need to lock the CLI in the workflows in case we ever have a breaking change on it, currently it installs the latest and if people use older version of the workflows when there is a breaking change it will break that workflow accidentally.
The text was updated successfully, but these errors were encountered:
wolfenrain
added
bug
Something isn't working as expected
feature
A new feature or request
and removed
bug
Something isn't working as expected
labels
Nov 7, 2022
Rather than exposing an input to customize very_good_cli in the workflow shouldn't we treat breaking changes in very_good_cli as breaking changes in the workflow? I would rather not expose inputs in the workflow that tightly couple the workflow to very_good_cli since in the future we may decide to move away from very_good_cli (it's an internal implementation detail imo).
Description
We need to lock the CLI in the workflows in case we ever have a breaking change on it, currently it installs the latest and if people use older version of the workflows when there is a breaking change it will break that workflow accidentally.
The text was updated successfully, but these errors were encountered: