Skip to content

CI: add build step to validate that pubspecs do not include dependency_overrides #220

Closed
Closed
CI: add build step to validate that pubspecs do not include dependency_overrides#220

Description

@FlutterIssues
FlutterIssues
opened on Nov 9, 2015

Issue by sethladd
Thursday Oct 22, 2015 at 23:07 GMT
Originally opened as https://github.com/flutter/engine/issues/1747

We noticed that some code reviews notice that the pubspec.yaml has a dependency_override mention. Would it help to add a small step to the Travis build that fails when it notices a dependency_override in any pubspec.yaml ?

Activity

  1. FlutterIssues commented on Nov 9, 2015

    @FlutterIssues
    FlutterIssues
    on Nov 9, 2015
    Author

    Comment by abarth
    Thursday Oct 22, 2015 at 23:25 GMT

    We use dependency_override in packages that we don't intend to publish to pub... Maybe there's a better way?

  2. abarth commented on Nov 18, 2015

    @abarth
    abarth
    on Nov 18, 2015
    Contributor

    This issue seems obsolete.

  3. abarth
    closed this as completedon Nov 18, 2015

  4. github-actions commented on Sep 7, 2021

    @github-actions
    github-actionsbot
    on Sep 7, 2021

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  5. github-actions
    locked as resolved and limited conversation to collaborators on Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions