Closed zamnuts closed 3 years ago
There is an auto update workflow that should kickoff, if we want we can manually push to each version in the .version to have it built and pushed respectively.
I'm only able to find the scheduler workflow which runs 10am daily.
Only the latest version is considered, which means we'll lose already released versions, and have to wait for the upstream to push first.
I vote we manually push each version:
3.0.3
(ignoring 3.0.1 and 3.0.2)4.0.0
, which will also become latest
Thanks @xUnholy, I see the new ones published to hub, and was able to pull and run them on a handful of rk3399 cpus :+1:
Brilliant that is great news, once again thank you for the great contributions!
Details
What steps did you take and what happened:
Image versions listed for
csi-external-snapshotter
are missing3.0.3
and4.0.0
on docker hub raspbernetes/csi-external-snapshotter.However, versions
3.0.0
(oldest 3.x) and2.1.4
(latest 2.x) do exist on docker hub.Additionally,
latest
points to2.1.4
. Upon updating, should this point to3.0.3
,4.0.0
or the latest 2.x stable (2.1.4
)? PR #206 fixed the build for csi-external-snapshotter (see #205), but accidentally made version2.1.4
aliased bylatest
, despite3.0.0
being the previouslatest
. This will cause a downgrade on subsequent pulls for those using thelatest
tag.What did you expect to happen:
Versions 3.0.3 and 4.0.0 should be made available, and maybe
latest
should alias4.0.0
.Additional Information:
In what order should the
.version
file be updated?