Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(manager/gitlabci): support registry aliases #28607

Merged
merged 2 commits into from
Apr 24, 2024

Conversation

candrews
Copy link
Contributor

Changes

Applies registry aliases in the the GitLab CI manager.

Context

The GitLab CI manager should support registry aliases like many of the other managers already do.

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@candrews candrews marked this pull request as draft April 23, 2024 20:30
lib/modules/manager/gitlabci/extract.ts Outdated Show resolved Hide resolved
Co-authored-by: Sebastian Poxhofer <secustor@users.noreply.github.com>
@candrews candrews requested a review from secustor April 24, 2024 12:59
@secustor secustor changed the title feat(gitlabci): support registry aliases feat(manager/gitlabci): support registry aliases Apr 24, 2024
@secustor secustor added this pull request to the merge queue Apr 24, 2024
Merged via the queue into renovatebot:main with commit eb87cbb Apr 24, 2024
37 checks passed
@@ -120,6 +120,7 @@ function getAllIncludeComponents(

function extractDepFromIncludeComponent(
includeComponent: GitlabIncludeComponent,
registryAliases?: Record<string, string>,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
registryAliases?: Record<string, string>,
registryAliases: Record<string, string> | undefined,

I had preferred this

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll keep that in mind for the future... but this has already been merged so what, if anything, should be done now?

@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 37.321.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants