ci: Use meson introspect to generate artifact path

We currently assume that the `CI_COMMIT_TAG` variable matches the
version component of the generated dist tarball.

That is usually correct, but sometimes errors happen and a wrong
tag is pushed, and the real release uses something like "46.0-real".

Account for that by building the artifact path from `meson introspect`
and exporting it as environment variable.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/324>

.gitlab-ci.yml

@@ -147,6 +147,21 @@ fedora-build:
     paths:
       - build
 
+fedora-distinfo:
+  stage: deploy
+  needs:
+    - fedora-build
+  script:
+    - .gitlab-ci/export-artifact-path build > dist.env
+  artifacts:
+    reports:
+      dotenv: dist.env
+    paths:
+      - build
+      - dist.env
+  rules:
+    - if: '$CI_COMMIT_TAG'
+
 fedora-dist:
   stage: deploy
   needs:
@@ -163,9 +178,13 @@ fedora-dist:
 
 fedora-dist-tarball:
   extends: fedora-dist
+  needs:
+    - fedora-distinfo
   artifacts:
     expose_as: 'Get tarball here'
     paths:
-      - build/meson-dist/$CI_PROJECT_NAME-$CI_COMMIT_TAG.tar.xz
+      - $TARBALL_ARTIFACT_PATH
+    reports:
+      dotenv: dist.env
   rules:
     - if: '$CI_COMMIT_TAG'

.gitlab-ci/export-artifact-path

@@ -0,0 +1,21 @@
+#!/usr/bin/gjs -m
+// SPDX-FileCopyrightText: 2024 Florian Müllner <fmuellner@gnome.org>
+//
+// SPDX-License-Identifier: GPL-2.0-or-later
+
+import Gio from 'gi://Gio';
+import {programArgs, programInvocationName, exit} from 'system';
+
+const [buildDir] = programArgs;
+if (!buildDir) {
+    printerr(`usage: ${programInvocationName} <build-dir>`);
+    exit(1);
+}
+
+const subprocess = Gio.Subprocess.new(
+    ['meson', 'introspect', '--projectinfo', buildDir],
+    Gio.SubprocessFlags.STDOUT_PIPE);
+const [, out] = subprocess.communicate_utf8(null, null);
+
+const {descriptive_name, version} = JSON.parse(out);
+print(`TARBALL_ARTIFACT_PATH=${buildDir}/meson-dist/${descriptive_name}-${version}.tar.xz`);