fix(ci): add --no-example flag to dart pub get in publish workflow#19
Merged
dhruvanbhalara merged 1 commit intomainfrom Mar 18, 2026
Merged
fix(ci): add --no-example flag to dart pub get in publish workflow#19dhruvanbhalara merged 1 commit intomainfrom
dhruvanbhalara merged 1 commit intomainfrom
Conversation
Updated the install dependencies step to exclude examples.
dhruvanbhalara
changed the title
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
1 participant
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.
Summary
Fixes the
publish.yamlCI workflow by adding the--no-exampleflag to thedart pub getstep, preventing it from resolving dependencies for the example project during the publishing pipeline.Changes
.github/workflows/publish.yaml: Updated theInstall dependenciesstep fromdart pub gettodart pub get --no-example.Why
The example project may have Flutter-specific dependencies that are not resolvable in a pure Dart SDK environment. Since the publish workflow only needs the library's own dependencies, skipping example resolution avoids unnecessary failures.