Skip to content

[flutter_plugin_tools] ci should make sure all plugins are published. #92675

@cyanglaz

Description

@cyanglaz

The release ci fails silently since it sometimes fails to block the tree. This causes plugins fail to be published and it requires real people to check the "release ci" in all the past commits to make sure they are published.

There are 2 things (or more) we can do:

  1. When release ci fails, send an email to the plugin/ecosystem team to notify the failure.
  2. Add a new ci check to make sure all the plugins are published at HEAD~.

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