Have noticed recently that when a new latest image is published, a new stable image is also published even though no new update for stable is ready.
Could help reduce build system costs, and improve auto/semi-auto update mechanisms by only triggering a branch build it that specific branch has received a change.
Have noticed recently that when a new latest image is published, a new stable image is also published even though no new update for stable is ready.
Could help reduce build system costs, and improve auto/semi-auto update mechanisms by only triggering a branch build it that specific branch has received a change.
Is this something that can be addressed?