Pin @gitlab/ui to v16.0.0
What does this MR do?
The @gitlab/ui package was recently upgraded to v16.0 which doesn't seem to please Renovate as it has opened an MR to pin the package to v16.0.0: !33106 (closed)
Unfortunately, there seems to be a bug with how Renovate pins dependencies on GitLab, which is causing those MRs to be constantly rebased, preventing us from merging them.
We've had this problem occur quite recently when @gitlab/ui was accidentally unpinned, and Renovate triggered 31 consecutive pipelines on the same MR: !32749 (closed).
The present MR manually pins the dependency so that we are able to merge the change. Once this is merged, Renovate will automatically close its MR.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team