.gitlab-ci.yml: Switch to rules for determining when to run a pipeline and limit dist run to tags

https://docs.gitlab.com/ee/ci/jobs/job_control.html

We're currently using only which is deprecated:

This:

• moves us to rules from only
• makes the dist pipeline only run for tags, as we don't want it to run twice (<which breaks the api repo somehow) when we create a release branch and a tag simultaneously. we also don't want to modify a release post-release without bumping the release number (v1.3.1 vs v1.3.0) as otherwise we sacrifice user (updates) and dev (people who git switch v1.3.0) friendliness.

changed title from .gitlab-ci.yml: Switch to rules for determining when to run a pipeline to .gitlab-ci.yml: Switch to rules for determining when to run a pipeline and limit dist run to tags

added 2 commits

• 9b19c434 - 1 commit from branch main
• aa4b98c0 - .gitlab-ci.yml: Switch to rules/if

Compare with previous version

this looks wildly simpler than the regex (?) it replaces, how come?

We don't want to trigger this on release branches, only tags.

makes the dist pipeline only run for tags, as we don't want it to run twice (<which breaks the api repo somehow) when we create a release branch and a tag simultaneously. we also don't want to modify a release post-release without bumping the release number (v1.3.1 vs v1.3.0) as otherwise we sacrifice user (updates) and dev (people who git switch v1.3.0) friendliness.

The only->rules change is due to only being deprecated.

added 17 commits

• aa4b98c0...385e7500 - 16 commits from branch main
• dc6c121b - .gitlab-ci.yml: Switch to rules/if

Compare with previous version

enabled an automatic merge when the pipeline for dc6c121b succeeds

merged