-
Notifications
You must be signed in to change notification settings - Fork 6
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
have a way to configure publishing dry run checks #64
Comments
Fwiw, if the ignore syntax is feasible it would be my preference. This would in general make publishing safer on packages that have known warnings (only new warnings would appear), and document those warnings that are known to exist. |
One other way we could configure this to ignore publishing warnings is by supporting something like a |
Right now some packages have intentional
dart pub publish --dry-run
warnings.firehose
fails the build on the dry-run checks; we may want some additional configurability here. See dart-lang/test#1923 for context.Some ideas are:
ignore: xxx
syntax in pubspec filesfirehose
to distinguish dry-run warnings vs errors and not fail builds for warnings (as pub is currently, any warnings sets an exit code of65
)The text was updated successfully, but these errors were encountered: