Test 30.1.0-beta5 release

Revertme

Test 30.1.0-beta4 release

WIP

Test 30.1.0-beta3 release

CI: Remove validateToPublish input

It's not used anymore.

Test beta release (27.2.0-beta5)

CI: Split Flatpak beta and stable branches

We currently publish the same build from the same branch
to Flathub. However, soon we'll need to build the Flatpak
manifest in different branches, and publish them in different
repositories.

Prepare for that by splitting the publish step in two: one
for Flathub, and another for Flathub Beta. Do that using
a matrix strategy.

Skip building and publishing stable releases when it's a beta
or RC release by setting an output variable in the first job.

Test beta release (27.2.0-beta4)

CI: Split Flatpak beta and stable branches

We currently publish the same build from the same branch
to Flathub. However, soon we'll need to build the Flatpak
manifest in different branches, and publish them in different
repositories.

Prepare for that by splitting the publish step in two: one
for Flathub, and another for Flathub Beta. Do that using
a matrix strategy.

Test beta release (27.2.0-beta3)

CI: Split Flatpak beta and stable branches

We currently publish the same build from the same branch
to Flathub. However, soon we'll need to build the Flatpak
manifest in different branches, and publish them in different
repositories.

Prepare for that by splitting the publish step in two: one
for Flathub, and another for Flathub Beta. Do that using
a matrix strategy.

Test beta release (27.2.0-beta2)

CI: Build Flatpak into different branches when publishing

When publishing to Flathub, we want to publish the 'beta'
branch to the 'beta' repository, and the 'stable' branch
to the 'stable' repository. However, we currently publish
the 'master' branch for both.

Build the Flatpak manifest with different branches for each
repository.

Test beta release (27.1.3-beta1)

test-27.1.3-beta1

foo

Test release 8 (27.1.3-rc1)

test-27.1.3-rc8

foo

Test release 6 (27.1.3-rc1)

test-27.1.3-rc6

foo