Skip to content

Pin gitlab-dangerfiles version

Nao Hashizume requested to merge nh/pin-gitlab-dangerfiles-version into main

What does this MR do?

This MR pins gitlab-dangerfiles version to 4.1.0 to fix danger-review job failure caused by a recent change in version 4.2.0 until gitlab-org/ruby/gems/gitlab-dangerfiles!233 (merged) is merged.

Example danger-review job failure: https://gitlab.com/gitlab-org/gitlab-runner/-/jobs/5264649101#L119.

Why was this MR needed?

What's the best way to test this MR?

What are the relevant issue numbers?

gitlab-org/ruby/gems/gitlab-dangerfiles#75 (closed)

Edited by Nao Hashizume

Merge request reports