Skip to content

flutter version gets confused on master with some configurations of Git history #50577

@dnfield

Description

@dnfield

Sometimes, a PR has to have its git history rewritten because the tool starts reporting some older version of Flutter with a very high .pre number. See for example #45035

The work around for this is to:

git fetch upstream
git reset --soft upstream/master
git commit -m 'rewrite history!'
git push -f

Or something like that. This gets the version output back to normal on CI.

Ideally, the tool would be able to handle this situation. I'm not as familiar with its version logic though - @jonahwilliams maybe?

/cc @Piinks

Metadata

Metadata

Assignees

No one assigned

    Labels

    c: contributor-productivityTeam-specific productivity, code health, technical debt.toolAffects the "flutter" command-line tool. See also t: labels.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions