Skip to content

Flutter mac engine binaries should be codesigned on master branch #44372

Closed
Closed
Flutter mac engine binaries should be codesigned on master branch#44372
Assignees
godofredoc
Labels
P1High-priority issues at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.from: postmortemIssues identified as part of a postmortemteam-infraOwned by Infrastructure team‎‍platform-catalinaIssues related to macOS Catalina

Description

@christopherfujino
christopherfujino
opened on Nov 7, 2019

Currently, flutter macOS engine binaries are manually codesigned and notarized with Apple prior to each dev release. This issue is to track the process of automating this process for each Flutter engine commit (and thus making ensuring every framework commit on master has signed/notarized binaries).

Activity

  1. christopherfujino
    added
    c: contributor-productivityTeam-specific productivity, code health, technical debt.
    team-infraOwned by Infrastructure team
    on Nov 7, 2019
  2. christopherfujino
    assigned
    christopherfujino
    and
    godofredoc
    on Nov 7, 2019
  3. christopherfujino
    added
    ‎‍platform-catalinaIssues related to macOS Catalina
    on Nov 7, 2019
  4. digiter
    added
    passed secondary triage
    on Mar 26, 2020
  5. zanderso
    unassigned
    christopherfujino
    on Jun 18, 2020
  6. christopherfujino
    added
    from: postmortemIssues identified as part of a postmortem
    postmortem
    on May 1, 2021

  7. godofredoc commented on May 13, 2021

    @godofredoc
    godofredoc
    on May 13, 2021
    Contributor

    We can start with moving the release branch bots to chrome internal and build from there.

  8. godofredoc
    added
    P1High-priority issues at the top of the work list
    on May 13, 2021

  9. godofredoc commented on Dec 1, 2022

    @godofredoc
    godofredoc
    on Dec 1, 2022
    Contributor

    We are tracking the signing of binaries on release candidate branches. Closing as obsolete.

  10. godofredoc
    closed this as completedon Dec 1, 2022

  11. github-actions commented on Mar 5, 2023

    @github-actions
    github-actionsbot
    on Mar 5, 2023

    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.

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

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.from: postmortemIssues identified as part of a postmortemteam-infraOwned by Infrastructure team‎‍platform-catalinaIssues related to macOS Catalina

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions