3 commits

Author	SHA1	Message	Date
zeripath	e84a432f76	Make docker gitea/gitea:v1.16-dev etc refer to the latest build on that branch (#18551) (#18569) ... Backport #18551 (Backporting this will enable this target to create 1.16-dev) One of the problems with our current docker tagging is that although we have strict version tags, latest and dev we do not have a way for docker users to track the current release branch. This PR simply suggests that we use the 1.x-dev tag for these and we build and push these. This will give users who want or need unreleased bug fixes the option of tracking the pre-release version instead of simply jumping to dev. (Also contains backport for #18573) Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: KN4CK3R <admin@oldschoolhack.me> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>	2022-02-03 12:00:33 +00:00
techknowlogick	e180456983	Change docker tag logic (#16421) ... * Change docker logic * Apply suggestions from code review Co-authored-by: Kyle D. <kdumontnu@gmail.com> * docs Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lauris BH <lauris@nix.lv> Co-authored-by: Kyle D. <kdumontnu@gmail.com>	2021-07-14 18:08:43 +01:00
Antoine GIRARD	d4667a4949	drone/docker: prepare multi-arch release + provide arm64 image (#7571) ... * drone/docker: prepare multi-arch release * Add docker-linux-arm64 pipeline * add arm 64 build to manifest * tag dry-run + indent * Fix notify dependency	2019-07-24 13:21:12 -04:00