Conversation
Package publishing
Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation. |
PR HealthLicense Headers ✔️
All source files should start with a license header. Unrelated files missing license headers
This check can be disabled by tagging the PR with API leaks ✔️The following packages contain symbols visible in the public API, but not exported by the library. Export these symbols or remove them from your publicly visible API.
This check can be disabled by tagging the PR with Breaking changes ✔️
This check can be disabled by tagging the PR with Coverage ✔️
This check for test coverage is informational (issues shown here will not fail the PR). This check can be disabled by tagging the PR with Changelog Entry ✔️
Changes to files need to be accounted for in their respective changelogs. This check can be disabled by tagging the PR with |
| @@ -1,10 +1,12 @@ | |||
| ## 6.1.0-wip | |||
| ## 6.1.0 | |||
There was a problem hiding this comment.
In the past we've considered it a breaking change to add lints (because it can surface new warnings that may break people's CI) and the policy was to do major version bump for those. Did the policy change?
FWIW, I can't find this written down in the lints package, but we documented it on the flutter_lints package:
Adding a lint to the package may create new warnings for existing users and is therefore considered to be a breaking change, which will require a major version bump.
There was a problem hiding this comment.
Did the policy change?
Not officially. Future publishes should follow the old procedure.
#923 (comment)
Closes #832