Skip to content

Commit

Permalink
Repair Kread since we're upgrading Zoe (#10327)
Browse files Browse the repository at this point in the history
refs: #10267

## Description

We'll be upgrading Zoe in the next SW upgrade. We need to reset the KREAd subscribers when we do that.

### Security Considerations

No broader security implications

### Scaling Considerations

Not a scaling concern

### Documentation Considerations

I should have remembered this when adding the Zoe upgrade.

### Testing Considerations

None

### Upgrade Considerations

There's a constraint that we need to enforce when we upgrade Zoe. So far, we've been remembering it, but it would be better to automate.
  • Loading branch information
mergify[bot] authored Oct 24, 2024
2 parents a67502b + df51360 commit 1cb7915
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions golang/cosmos/app/upgrade.go
Original file line number Diff line number Diff line change
Expand Up @@ -158,6 +158,10 @@ func unreleasedUpgradeHandler(app *GaiaApp, targetUpgrade string) func(sdk.Conte
// Upgrade Zoe (no new ZCF needed).
"@agoric/builders/scripts/vats/upgrade-zoe.js",
),
// Revive KREAd characters
vm.CoreProposalStepForModules(
"@agoric/builders/scripts/vats/revive-kread.js",
),
vm.CoreProposalStepForModules(
// Upgrade to new liveslots for repaired vow usage.
"@agoric/builders/scripts/vats/upgrade-orch-core.js",
Expand Down

0 comments on commit 1cb7915

Please sign in to comment.