Keeping the same IPNS release name on a new publisher
Moving a release job to a second Kubo node can accidentally create a second public name. IPNS derives the name from a key; the key alias in a deployment script is local to the repository.
Check the public identifier before publishing
Use a test release name you control. Set RELEASE_NAME to its existing public identifier and NEW_ROOT to a directory CID that can be retrieved. In the first command’s output, compare the public identifier beside KEY_ALIAS with the saved identifier. Run the publish command only if they match. Creating another key with the same alias will produce a different identifier.
ipfs key list -l
ipfs name publish --key="$KEY_ALIAS" "/ipfs/$NEW_ROOT"
ipfs name resolve "/ipns/$RELEASE_NAME"
Resolve the name that users already have
Use the saved public name for the final read and repeat from an independent node after propagation. Resolving the name printed by the new job would only test whichever key it just used. If the old name still resolves to the old target, inspect the publishing node’s key and record validity. Retain the new content independently so successful resolution also leads to retrievable bytes.