-
Notifications
You must be signed in to change notification settings - Fork 74
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
feat: lock very_good_cli version in workflow #101
Conversation
…workflows into chore/lock-cli-version
@@ -43,6 +43,10 @@ on: | |||
required: false | |||
type: boolean | |||
default: false | |||
very_good_cli_version: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comment on #90 (comment) about not tightly coupling the public API of the workflow to very_good_cli since very_good_cli is just an implementation detail imo. I think we should instead just restrict the workflow to a specific version range dart pub global activate very_good_cli <0.2.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comments and lmk what you think
Closing this in favor of this comment |
Description
I added an input which locks the very_good_cli version, in case of breaking changes. Closes #90 .
Type of Change