Repository navigation
test: enforce full coverage and upgrade workspace dependencies - #45
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every runnable workspace package now has a coverage gate requiring 100% executable line coverage, including examples, CLI entrypoints, Mason hooks, repository tools, and native permission-plugin sources. The gate fails on missing tests, empty reports, or missing executable source records. Regression tests also fixed broken DZod refinements, asynchronous validation, and example/lifecycle behavior.
Dependencies are upgraded to their latest compatible versions across Dart/Flutter packages, generated templates, Node tooling, and the Android plugin. The repository now uses a native Dart workspace with Melos 8 and a shared lockfile. CI enforces formatting, analysis, coverage, and native tests; root dependency changes also trigger generated-template validation.
Local validation
git diff --checkpassed.Compatibility notes
melos.yamltopubspec.yaml.Schema<String>instead of throwing invalid casts; string-specific checks should precede these refinements.Per-package coverage report and reproduction details.