# Improving image publication workflow

**URL:** https://forum.duniter.org/t/improving-image-publication-workflow/10839
**Category:** Duniter-v2s
**Tags:** docker
**Created:** [19 March 2023 13:58 UTC](https://forum.duniter.org/t/improving-image-publication-workflow/10839 "2023-03-19T13:58:53Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![HugoTrentesaux](https://forum.duniter.org/user_avatar/forum.duniter.org/hugotrentesaux/32/6396_2.png) [@HugoTrentesaux](https://forum.duniter.org/u/HugoTrentesaux)
#### Post date: [21 March 2023 11:39 UTC](https://forum.duniter.org/t/improving-image-publication-workflow/10839/7 "2023-03-21T11:39:49Z")

</div>

Part of the discussion about how to improve the image publication workflow happened in this thread: [Release new image with ĞDev5 chainspecs](https://forum.duniter.org/t/release-new-image-with-gdev5-chainspecs/10723)

If I try to summarise :

- we have to make sure that the “latest” label connects to current ĞDev network
- we should refactor the CI to only publish images when wanted, and with correct tag
- in the future, we could also have “gtest” and “g1” labels that connect to the respective network

We also have to define how we will be naming Duniter client versions. For example, right now, the only version labeled `v0.4.1` is available in image `duniter/duniter-v2s:sha-2be3f534`.

---

_[View the full topic](https://forum.duniter.org/t/improving-image-publication-workflow/10839)._