cafkafk/lix - git.fem.gg: Rust + Nix = ???

cafkafk/lix

Fork 0

Commit graph

Author	SHA1	Message	Date
Jade Lovelace	8a86f38bca	Fix is_maintenance_branch heuristic This was broken because Nix language's version comparison does not know how to deal with versions like -rc1 and considers them newer, which is in this case not desirable. That in turn led to not tagging 2.90.0 docker images as "latest" since the heuristic was wrong. This commit also adds some more cross-checking and failsafes in case the person running releng does not have a local main branch that is up to date. Fixes: https://git.lix.systems/lix-project/lix/issues/443 Change-Id: I537103ebab58ae978c00e06972abe14432dd9c80	2024-08-07 20:14:45 -07:00
Jade Lovelace	7be0d237e0	releng: fix git checking Change-Id: I82ddd918311b48e596adb807b81221973113fe7a	2024-06-13 15:24:21 -07:00
Jade Lovelace	ce71d0e9ab	releng: automatically figure out if we should tag latest for docker For example, when releasing from release-2.90, if `main` has a 2.91 tag ancestor, we know that 2.91 was released, so we should not tag latest. Change-Id: Ia56b17a2ee03bbec74b7c271c742858c690d450d	2024-06-09 20:33:24 -07:00

Author

SHA1

Message

Date

Jade Lovelace

8a86f38bca

Fix is_maintenance_branch heuristic

This was broken because Nix language's version comparison does not know
how to deal with versions like -rc1 and considers them newer, which is
in this case not desirable.

That in turn led to not tagging 2.90.0 docker images as "latest" since
the heuristic was wrong.

This commit also adds some more cross-checking and failsafes in case the
person running releng does not have a local main branch that is up to
date.

Fixes: https://git.lix.systems/lix-project/lix/issues/443
Change-Id: I537103ebab58ae978c00e06972abe14432dd9c80

2024-08-07 20:14:45 -07:00

Jade Lovelace

7be0d237e0

releng: fix git checking

Change-Id: I82ddd918311b48e596adb807b81221973113fe7a

2024-06-13 15:24:21 -07:00

Jade Lovelace

ce71d0e9ab

releng: automatically figure out if we should tag latest for docker

For example, when releasing from release-2.90, if `main` has a 2.91 tag
ancestor, we know that 2.91 was released, so we should *not* tag latest.

Change-Id: Ia56b17a2ee03bbec74b7c271c742858c690d450d

2024-06-09 20:33:24 -07:00

3 commits