# Registry image tag for major versions

**URL:** <https://discourse.nodered.org/t/registry-image-tag-for-major-versions/101547>\
**Category:** Core Development\
**Tags:** docker\
**Created:** [28 July 2026 09:49 UTC](https://discourse.nodered.org/t/registry-image-tag-for-major-versions/101547 "2026-07-28T09:49:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![simonjamain](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/simonjamain/32/108094_2.png) [@simonjamain](https://discourse.nodered.org/u/simonjamain)\
**Post date:** [28 July 2026 09:49 UTC](https://discourse.nodered.org/t/registry-image-tag-for-major-versions/101547/1 "2026-07-28T09:49:50Z")

</div>

## Context

> We have several docker/portainer-managed nodered instances on docker VMs (along many other containers). We want/need to update regularly our containers images.

## Use case

> We want to update minor versions of our nodered images (semi)automatically, to reduce the burden of maintaining updates.

## Solution proposed

> The introduction of a new registry tag holding only the major version (keeping and ofc) would fit into our existing logic and allow us to easily update for minor changes automatically.  
> Examples of images with this principle :
> 
> - nginx : https...hub.docker.com/layers/library/nginx/1
> - traefik : https...hub.docker.com/layers/library/traefik/3

To clarify, what this proposal would do is to add docker image tags with minor/patch versionning stripped out (existing ones) for exemple : `5`, `5-24-minimal`, `5-24`, etc

I actually made an issue first [No registry image tag for major versions · Issue #525 · node-red/node-red-docker](https://github.com/node-red/node-red-docker/issues/525) but I was suggested to discuss it here before, i also have the PR ready Pull Request #526

---

<div class="post-metadata">

**Author:** ![aitor](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/aitor/32/97363_2.png) [@aitor](https://discourse.nodered.org/u/aitor)\
**Post date:** [28 July 2026 10:00 UTC](https://discourse.nodered.org/t/registry-image-tag-for-major-versions/101547/2 "2026-07-28T10:00:39Z")

</div>

Welcome to the forum!

Have you looked into Node-RED Projects yet? [Projects : Node-RED](https://nodered.org/docs/user-guide/projects/)

A common approach is to use Projects with development containers, commit flow changes to your own repository, automate container builds through your CI/CD pipeline, and then deploy updates with a simple script or automation workflow.

This works especially well in multi-container environments, as it gives you a more reliable deployment process.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [28 July 2026 10:18 UTC](https://discourse.nodered.org/t/registry-image-tag-for-major-versions/101547/3 "2026-07-28T10:18:56Z")

</div>

@aitor this is not related to the Projects feature. It's purely about what tags we publish the project docker containers under.

@simonjamain thanks for the PR - we'll get it reviewed and merged before the next maintenance release.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [26 September 2026 10:19 UTC](https://discourse.nodered.org/t/registry-image-tag-for-major-versions/101547/4 "2026-09-26T10:19:22Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.