bryanlabs/cosmos-upgrades

Issues

• Error gathering data from chains using gov v1

  #42 opened 8 days ago by pharr117
  0

• Quasar reporting

  #41 opened 6 months ago by danbryan
  0

• Chains missing estimated_upgrade_time when upgrade is found

  #35 opened a year ago by joshlopes
  1

• Suggestion: More fields

  #36 opened a year ago by joshlopes
  1

• Active Proposal endpoints are not available for chains that do not use gov, skip Active Proposal check for these chains

  #34 opened a year ago by pharr117
  0

• REST Health checks are failing in multiple ways, either fix or eliminate health checks

  #33 opened a year ago by pharr117
  0

• Semver matching function is matching on pre-release tags when it should skip those

  #32 opened a year ago by pharr117
  0

• Implement production ready setup with reader/writer worker split

  #30 opened a year ago by pharr117
  1

• Datetime format string error during update loop

  #27 opened a year ago by pharr117
  2

• Add gh_commit to output

  #24 opened a year ago by danbryan
  0

• Handle active upgrade proposals while a current plan is already in place

  #23 opened a year ago by pharr117
  1

• Handle multiple upgrade proposals

  #22 opened a year ago by pharr117
  0

• Use plan name and search on repo git tags to find potential versions

  #18 opened a year ago by pharr117
  0

• email integration

  #16 opened a year ago by danbryan
  0

• rework semantic version match

  #10 opened a year ago by danbryan
  0

• bug: some chains don't check for upgrades.

  #9 opened a year ago by danbryan
  2

• Add support for block-height to UTC time

  #3 opened a year ago by danbryan
  0

• Add support for upgrade name (cosmosvisor)

  #2 opened a year ago by danbryan
  0

• persist chain registry data

  #6 opened a year ago by danbryan
  2

• Add example of how to filter the requests from mainnets

  #4 opened a year ago by danbryan
  0