# Publishing collections through Zuul currently not working

**URL:** <https://forum.ansible.com/t/publishing-collections-through-zuul-currently-not-working/44197>\
**Category:** Collection Development\
**Tags:** news-for-maintainers, zuul, collections\
**Created:** [August 3, 2025, 8:08am UTC](https://forum.ansible.com/t/publishing-collections-through-zuul-currently-not-working/44197 "2025-08-03T08:08:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [August 3, 2025, 8:08am UTC](https://forum.ansible.com/t/publishing-collections-through-zuul-currently-not-working/44197/1 "2025-08-03T08:08:57Z")

</div>

It looks like publishing collections through Zuul ([Zuul](https://ansible.softwarefactory-project.io/zuul/status)) is currently broken. The publishing step tries to install ansible-core devel in a Python 3.11 venv, which no longer works. There seems to be a PR that might fix this ([Remove temporary work around to publish a collection by GomathiselviS · Pull Request #602 · ansible/zuul-config · GitHub](https://github.com/ansible/zuul-config/pull/602)), but it hasn’t been merged yet.

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [August 3, 2025, 1:25pm UTC](https://forum.ansible.com/t/publishing-collections-through-zuul-currently-not-working/44197/2 "2025-08-03T13:25:40Z")

</div>

I think now might be the time to move from Zuul to GitHub Action. It’s something we are looking at doing as part of simplifying ISV Partners repos being published to Galaxy & Hub

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [August 3, 2025, 1:43pm UTC](https://forum.ansible.com/t/publishing-collections-through-zuul-currently-not-working/44197/3 "2025-08-03T13:43:38Z")

</div>

That would be nice, but I’m not sure how this can be done in a safe way. IIRC in Galaxy you can only have a token for the whole `community` namespace, and not one for individual collections. If that’s still the case, using GHA sounds pretty dangerous.

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [August 4, 2025, 4:38pm UTC](https://forum.ansible.com/t/publishing-collections-through-zuul-currently-not-working/44197/4 "2025-08-04T16:38:59Z")

</div>

The PR has been merged, and releasing works again! Thanks 🙂

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [August 4, 2025, 5:20pm UTC](https://forum.ansible.com/t/publishing-collections-through-zuul-currently-not-working/44197/5 "2025-08-04T17:20:23Z")

</div>

> [@gundalow](#):
>
> I think now might be the time to move from Zuul to GitHub Action.

Maybe start a new thread on this? Or do we already have and I’ve overlooked it?