Earl Warren 854be47328 [CI] Forgejo Actions based release process ... Refs: https://codeberg.org/forgejo/website/pulls/230 (cherry picked from commit 87d56bf6c7) [CI] Forgejo Actions based release process (squash) base64 -w0 to avoid wrapping when the doer name is long as it creates a broken config.json (cherry picked from commit 9efdc27e49) [CI] Forgejo Actions based release process (squash) generate .xz files and sources Generate .xz files Check .sha256 Generate the source tarbal (cherry picked from commit 7afec520c4) [CI] Forgejo Actions based release process (squash) release notes (cherry picked from commit d8f4f4807b) [CI] Forgejo Actions based release process (squash) publish and sign release (cherry picked from commit a52778c747) (cherry picked from commit cf2ec62740) [CI] Forgejo Actions based release process (squash) version use Actions environment variables in Makefile (#25319) (#25318) uses Actions variable to determine the version. But Forgejo builds happen in a container where they are not available. Do not use them. Also verify the version of the binary is as expected for sanity check. (cherry picked from commit 6decf111a1) (cherry picked from commit 206d0b3886) [CI] read STORED_VERSION_FILE if available (cherry picked from commit af74085ebf) [CI] backward compatible executable compilation Add a new static-executable target to use in Dockerfiles and restore the $(EXECUTABLE) target to what it was before to for backward compatibility. The release process now builds static executables instead of dynamically linked ones which makes them more portable. It changes the requirements at compile time and is not backward compatible. In particular it may break packaging that rely on the target that currently creates a dynamically linked executable. (cherry picked from commit 84d02a174a)		2023-07-03 07:39:52 +02:00
..
build-release	[CI] Forgejo Actions based release process	2023-07-03 07:39:52 +02:00
publish-release	[CI] Forgejo Actions based release process	2023-07-03 07:39:52 +02:00