Repository navigation
release: cli_util v0.6.0 - #2545
Conversation
Package publishingIf you have publishing permissions, you can use the links below to publish the changes after merging this PR.
Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation. |
PR HealthUnused Dependencies ✔️
For details on how to fix these, see dependency_validator. This check can be disabled by tagging the PR with Breaking changes ✔️
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 Changelog Entry ✔️
Changes to files need to be accounted for in their respective changelogs. This check can be disabled by tagging the PR with License Headers ✔️
All source files should start with a license header. 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 |
|
Was this rolled to google3? |
you ask amazing questions! |
|
@natebosch will do this NOW! |
|
Oh, we have a policy to roll into g3 before releasing for this repo? (I am package owner but seem to not be aware of this 😄) |
We have this policy for all We may need to think about how to socialize this more... |
|
Vibe up a BLOCKER action/workflow thingy requiring a label "I-solemnly-swear-this-has-rolled-to-the-sdk-and-google3"!! |
|
...before we allow a stable release PR to land? |
Prepare
cli_util0.6.0 release: