fix: update NodeInfra references after GitHub org migration - #22
Merged
areshand merged 1 commit intoAug 8, 2026
Merged
Conversation
areshand
marked this pull request as ready for review
August 6, 2026 00:15
ganymedio
approved these changes
Aug 6, 2026
musitdev
approved these changes
Aug 6, 2026
areshand
force-pushed
the
agent/fix-movement-network-references
branch
from
August 8, 2026 22:10
70978fe to
1d08220
Compare
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
3 participants
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.
What
Why
The old GHCR namespace no longer serves the migrated aptos-node images, so new NodeInfra deployments can fail while pulling the image or downloading genesis artifacts.
Impact
New deployments use ghcr.io/movement-network/aptos-node and movement-network/movement-networks. This PR does not change any live Kubernetes cluster.
Checks