feat(manager/composer): Use bitbucket-tags for vcs repos if it has bitbucket.org URL

[BernhardK91]

Changes

Currently, all "vcs" repositories (repositories added via git URL instead of using a provider like packagist) use git-tags. Unfortunately, this is not working with Bitbucket and result in authentication issues.

This PR adds a regex-based check if it is a Bitbucket URL and declares to use the bitbucket-tags datasource. If it is not, the current behavior stays unchanged.

The credentials (if needed) are used from username and password if platform is set to "bitbucket". Otherwise, you can use hostRules to set the credentials f.e. as followed:

hostRules: [
        {
            matchType: "bitbucket-tags",
            matchHost: "bitbucket.org",
            username: process.env.RENOVATEBOT_USERNAME,
            password: process.env.RENOVATEBOT_PASSWORD,
        }
    ],

Context

• Private Bitbucket packages try to fetch from packagist #24065.
• As suggested by @rarkins, I have oriented on the implementation for flux and also used the regex from there.

  renovate/lib/modules/manager/flux/extract.ts

  Lines 136 to 142 in 151435a

  	const bitbucketMatchGroups = bitbucketUrlRegex.exec(gitUrl)?.groups;
  	if (bitbucketMatchGroups) {
  	dep.datasource = BitbucketTagsDatasource.id;
  	dep.packageName = bitbucketMatchGroups.packageName;
  	dep.sourceUrl = `https://bitbucket.org/${dep.packageName}`;
  	return;
  	}

Closes #24065.

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

I have also tried with invalid credentials, and it failed as expected (to prove hostRules have an actual effect).

Note: This is my first PR at renovate, and I never worked with TypeScript before. So I am open for any suggestions or contributions to make this PR ready to merge if it is not already.

[CLAassistant]

All committers have signed the CLA.

[BernhardK91]

Sorry for asking this question. Do I understand that right, that the PR gets merged as soon as it has tests that cover the new feature?

If so, I will try my best to contribute some. But I never worked with jest before. Perhaps anyone can guide me how I can check the coverage locally without running all the tests.

[rarkins]

Yes, it's set to automerge once tests pass, and that requires 100% unit test coverage

[BernhardK91]

I have added a test, that should cover the change. Unfortunately, my commits disabled the auto-merge, so I cannot see if it really fixed the coverage.

As far as I can see locally, it should. At least it was on 100% when I ran jest /lib/modules/manager/composer/ --coverage --collectCoverageFrom=lib/modules/manager/composer/schema.ts after adding the new test.

[BernhardK91]

@rarkins Looks like Github had an issue what failed the Action. Can you requeue for merge? Thank you!

[renovate-release]

🎉 This PR is included in version 36.87.0 🎉

The release is available on:

• GitHub release
• 36.87.0

Your semantic-release bot 📦🚀