Skip to content

[package tooling] Move dart pub get into fetch deps command #130279

Closed

Description

@reidbaker

Newly created command for fetching/downloading dependencies prior to building named fetch-deps. Add dart pub get utility to the command to fetch dart dependencies.

Activity

  1. added
    p: toolingAffects the flutter_plugin_tools package
    packageflutter/packages repository. See also p: labels.
    fyi-ecosystemFor the attention of Ecosystem team
    and removed
    team-androidOwned by Android platform team
    fyi-ecosystemFor the attention of Ecosystem team
    on Jul 10, 2023
  2. stuartmorgan-g commented on Jul 13, 2023

    @stuartmorgan-g
    Contributor

    (I'm going to move this to team-ecosystem since if you didn't end up doing it after all, this is the right team for it.)

  3. added
    c: contributor-productivityTeam-specific productivity, code health, technical debt.
    P1High-priority issues at the top of the work list
    on Jul 13, 2023
  4. added
    team-androidOwned by Android platform team
    triaged-androidTriaged by Android platform team
    and removed
    team-androidOwned by Android platform team
    on Jul 13, 2023
  5. flutter-triage-bot commented on Jul 13, 2023

    @flutter-triage-bot

    The triaged-android label is irrelevant if there is no team-android label or fyi-android label.

  6. flutter-triage-bot commented on Dec 14, 2023

    @flutter-triage-bot

    This issue is marked P1 but has had no recent status updates.

    The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.

    Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!

  7. added
    P2Important issues not at the top of the work list
    and removed
    P1High-priority issues at the top of the work list
    on Dec 18, 2023
  8. stuartmorgan-g commented on Jan 8, 2026

    @stuartmorgan-g
    Contributor

    I did this in flutter/packages#4562

  9. github-actions commented on Jan 22, 2026

    @github-actions

    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.

  10. locked as resolved and limited conversation to collaborators on Jan 22, 2026
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

    P2Important issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.p: toolingAffects the flutter_plugin_tools packagepackageflutter/packages repository. See also p: labels.team-ecosystemOwned by Ecosystem teamtriaged-ecosystemTriaged by Ecosystem team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions