kolaente 4f8a44de89 fix(ci): switch release composite actions to unstable on non-tag builds ... The release-binaries and release-os-package composite actions were comparing the raw release-version input against the literal "main" to decide whether to use "unstable" for filenames and the S3 directory. Callers always pass `steps.ghd.outputs.describe`, which is a value like `v2.3.0-408-ge053d317` on non-tag builds — so the check never fired and unstable artifacts landed under `/<project>/<describe>/` with `<project>-<describe>-...` filenames. Drive the switch from `github.ref_type == 'tag'` instead, matching the pattern the desktop and config-yaml jobs in release.yml already use. The raw describe value still flows into RELEASE_VERSION so the binary and package metadata keep the precise commit reference.		2026-05-27 17:32:47 +02:00
..
release-binaries	fix(ci): switch release composite actions to unstable on non-tag builds	2026-05-27 17:32:47 +02:00
release-os-package	fix(ci): switch release composite actions to unstable on non-tag builds	2026-05-27 17:32:47 +02:00
setup-frontend	chore(deps): update actions/setup-node digest to 6044e13	2026-01-15 09:42:39 +01:00