Repository navigation
chore: sync Cosmopilot with upstream v2.2.1 history - #341
Merged
Merged
Conversation
…t them on init data
This file contains hidden or 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
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.
Sync Cosmopilot with upstream v2.2.1
Import upstream v2.2.1 at
fb46820so Nibiru can maintain and upstream patches against the same baseline mainnet currently deploys.Rationale
Nibiru's existing main branch,
40bc2c4, is an ancestor of upstream v2.2.1. This branch adds all 43 upstream commits with their original identities. It has no Nibiru functional changes or release customization.Key Changes
github.com/voluzi/cosmopilot/v2module andcosmopilot.voluzi.com/v1API, matching the current mainnet deployment.1 - History and release handling
Merge this history without squashing or rebasing it. The repo currently disables merge commits, so a reviewed fast-forward of main to this branch is the way to retain the exact upstream commit IDs under the current settings.
Upstream v2.1.0, v2.1.1, v2.2.0 and v2.2.1 operator/chart tags have been copied to the org under
upstream/, preserving their original objects without triggering release publishing. The unprefixedv2.2.1tag has also been published at the original upstream commit to produce the org baseline image and GitHub release. Other historical releases remain prefixed. Nibiru patch releases will use the publishing configuration in #342. Do not retarget upstream tags to org patch commits.The upstream unit suite and all 43 local integration specs pass. Full Docker/Kind E2E coverage runs in GitHub CI. This PR does not deploy anything to mainnet.