ci(halovisor): bump cosmovisor fork version #2322
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
corverroos
force-pushed
the
corver/fixhalovisor1
branch
from
ac0b15c
to
9703054
Compare
|
Docs preview complete 🚀 see it here: https://omni-h1t3lj3fi-omni-engineering.vercel.app |
ttarsi
approved these changes
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use the latest version of omni cosmovisor fork that fixes the restart issue by adding a custom current upgradeinfo flag so that the
upgrade_info.jsonthat cosmovisor writes after an upgrade is also persisted across docker container restarts.issue: fixes #2313