Skip to content

Handle multiple upgrade proposals #22

@pharr117

Description

@pharr117

Currently, the code finds the first upgrade proposal and uses that when reaching out to the /cosmos/gov/v1beta1/proposals?proposal_status=2 endpoint:

https://github.com/DefiantLabs/cosmos-upgrades/blob/18197052b24f9d07ddc1a9b0b8b9c80b1979d5e1/app.py#L272-L278

We should handle multiple upgrade proposals in case a chain has multiple active proposals being voted on.

We should consider whether the object data type is the best response value and maybe instead return an array of upgrade proposals in this case.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions