Skip to content

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

ave requested to merge ci-improvements into main

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

We're currently using only which is deprecated:

image

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.

Merge request reports