Milestones

List view

• Discoverability

  Start after every product task is done. Make ChainDiff findable from GitHub, PyPI, and the places node operators already read.

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• Network coverage

  One task per well-known network. The check uses that network's clients and that chain's upgrade schedule.

  No due date

  •12/12 issues closed
  100% complete0 open12 closed

• OP stack upgrades

  Track op-geth and op-node. OP Mainnet and Base each have their own network task for the upgrade schedule.

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• The node you actually run

  Answer the upgrade question for the execution and consensus clients installed on the machine, including the order a network upgrade requires.

  No due date

  •2/2 issues closed
  100% complete0 open2 closed

• Breaking-change advisories

  Review the releases operators are about to cross and record what actually breaks. A verdict of safe or not safe requires that review. ChainDiff does not mark a release reviewed on its own.

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• Configuration diff and deprecated flags

  Show which settings in the operator’s config will break or change on the target version. Every rule needs a source. A flag with no rule is not reported as safe.

  No due date

  •3/3 issues closed
  100% complete0 open3 closed