Release webhooks missing assets.links when created via CI/release-cli (release: keyword)

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

When a release is created via CI/CD using the release: keyword (release-cli), the initial “create” webhook payload omits assets.links, even though links are visible in the UI. Any subsequent “update” webhook (e.g., editing release notes) includes the links correctly.

Steps to reproduce

  1. Create a project with this .gitlab-ci.yml:
stages: [release]

release:
  image: registry.gitlab.com/gitlab-org/release-cli:latest
  stage: release
  script:
    - echo "Releasing"
  rules:
    - if: $CI_COMMIT_TAG
  release:
    tag_name: $CI_COMMIT_TAG
    description: "Test release"
    ref: "$CI_COMMIT_SHA"
    assets:
      links:
        - name: example-asset
          link_type: other
          url: https://example.com/download
          direct_asset_path: /binaries/linux-amd64
  1. Push a tag (git tag v0.0.1 && git push origin v0.0.1).
  2. Observe the “create” Release webhook payload.

Example Project

What is the current bug behavior?

The “create” webhook has assets.links: []. Only the auto-generated source archives are included. On editing the release notes, the “update” webhook correctly includes the links.

What is the expected correct behavior?

The “create” webhook should contain assets.links with the defined links.

Relevant logs and/or screenshots

image image

Related Issues

gitlab-org/cli#7859

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by 🤖 GitLab Bot 🤖