As part of a release workflow, the newly built collection is published to galaxy but this step produces an error: Run ansible-galaxy collection publish ./$NAMESPACE-$COLLECTION-$NEW_VERSION.tar.gz --api-key=*** ansible-galaxy collection publish ./$NAMESPACE-$COLLECTION-$NEW_VERSION.tar.gz --api-k…

@cloin We’ve deployed a patch that resolves the N namespace problem. I’ve also manually cleaned up your extra namespaces and fixed your account permissions. Please check again.

Namespace changed and collection upload not working

Get Help

tannerjc (James Tanner) October 4, 2023, 12:41am 5

@hikari661 please share your github username, and I will look into the issue.

2 Likes

Lost namespace's access

Topic		Replies	Views
Ansible-Galaxy Namespace Duplicated Collection Namespace Get Help galaxy-ng	20	136	March 14, 2025
Orphan namespaces Get Help galaxy-ng , namespace , bug	11	361	October 6, 2023
Roles namespace has changed with the new Galaxy website Get Help galaxy-ng , namespace	9	592	January 8, 2024
Incorrect namespaces name with 0 Get Help galaxy-ng , collections	4	206	December 12, 2023
Lost namespace's access Get Help galaxy-ng	6	383	October 22, 2023

Namespace changed and collection upload not working

Related topics