delete old log file if it exceeds kMaxLogFileSize of 25MiB

[christopherfujino]

Addresses flutter/flutter#150137

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[andrewkolos]

Out of curiosity, why use mutable fields for method implementations over optional constructor parameters? Do you find this more readable?

[andrewkolos]

LGTM

[github-actions]

Package publishing

Package	Version	Status	Publish tag (post-merge)
package:unified_analytics	6.1.2	ready to publish	unified_analytics-v6.1.2
package:cli_config	0.2.0	already published at pub.dev
package:extension_discovery	2.0.1-wip	WIP (no publish necessary)
package:graphs	2.3.2-wip	WIP (no publish necessary)

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

[devoncarew]

As an FYI, for the publishing automation we have set up for this repo, you generally either want to have the pubspec version end in -wip - to indicate that there are intentionally unpublished changes in the repo - or rev to the next approipriate semver version, land the PR, and then use the link in the publishing comment to publish that version.

Docs for this are at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

[christopherfujino]

or rev to the next approipriate semver version, land the PR, and then use the link in the publishing comment to publish that version.

Ahh, I missed the last step (link in the comment to publish). Thanks.