Failed to look up git-tags package warning

[Fab1n]

How are you running Renovate?

A Mend.io-hosted app

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

I get a warning on the renovate app:

The repo is a private repo, as accessible as every other repo (pretty sure).
It only has 1 tag (maybe this is the issue), which is the currently set version.

We scan a Package.swift and the dependency is found, according to the Github issue dashboard of Renovate.

What could be the issue?

Logs (if relevant)

Logs

{
  "datasource": "git-tags"
  "packageName": "<repo>"
  "err": {
    "task": {
      "commands": [
        "ls-remote",
        "<repo>"
      ],
      "format": "utf-8",
      "parser": "[function]"
    },
    "message": "remote: Repository not found.\nfatal: repository '<repo>' not found\n",
    "stack": "Error: remote: Repository not found.\nfatal: repository 'https://**redacted**@3.27.0/node_modules/simple-git/src/lib/plugins/error-detection.plugin.ts:42:29)\n    at PluginStore.exec (/usr/local/renovate/node_modules/.pnpm/simple-git@3.27.0/node_modules/simple-git/src/lib/plugins/plugin-store.ts:54:29)\n    at /usr/local/renovate/node_modules/.pnpm/simple-git@3.27.0/node_modules/simple-git/src/lib/runners/git-executor-chain.ts:124:42\n    at new Promise (<anonymous>)\n    at GitExecutorChain.handleTaskData (/usr/local/renovate/node_modules/.pnpm/simple-git@3.27.0/node_modules/simple-git/src/lib/runners/git-executor-chain.ts:121:14)\n    at GitExecutorChain.<anonymous> (/usr/local/renovate/node_modules/.pnpm/simple-git@3.27.0/node_modules/simple-git/src/lib/runners/git-executor-chain.ts:97:40)\n    at Generator.next (<anonymous>)\n    at fulfilled (/usr/local/renovate/node_modules/.pnpm/simple-git@3.27.0/node_modules/simple-git/dist/cjs/index.js:52:24)"
  }
}

[rarkins]

The git-tags datasource doesn't support authentication. Is it a github.com repo?

[Fab1n]

It is a github.com private organization repo. There is no authentication possible with HTTPS 😧?
I guess the SPM integration is git-tags only...

So the warning would be for every private repo, but the UI only shows the first error?

[rarkins]

You can try using overrideDatasource and overridePackageName

[Fab1n]

Can I use github-tags? Does this work?

[rarkins]

You might be the first to try, but it could

[github-actions[bot]]

Hi there,

A maintainer wants you to find and share a specific log message (packageFiles with updates) from your repository or environment.

If you self-host Renovate: make sure you run Renovate with LOG_LEVEL=debug to get the debug log messages! Next, open the debug-level logs and search for packageFiles with updates. This text marks the start of a structured log message that shows every package file, dependency, and update that Renovate found.

Find the relevant dependency/dependencies in the log message, and copy/paste those parts into this discussion. If you do not know which bits we need, you can copy/paste the full log message.

Read the Renovate docs, Troubleshooting to learn more about getting the docs, and getting the correct type of logs.

Thanks, the Renovate team

[Fab1n]

@rarkins there is no way of providing credentials to git-tags? Host rules don't work, either?

The Swift (SPM) integration only uses git-tags and I am surprised it doesn't support authentication. When I read the git-tags code and follow it I can see some resolving of host rules.

Sadly I was not able to debug it in docker due to some filesystem issues when running it in a container....

[Fab1n]

@rarkins I got it working. Our secret github token's account has not been added to the repository. I found it out of pure luck, because I saw that the other SPM (swift) packages using git-tag didn't contain any warning in the debug logs.

It was only one package, the one from the screenshot.

I added the machine account to the repo with "read" permission (the one where the token is attached to) and voilà, it works 🎉.

I also added one git-tag host rule in the UI, selecting the github token, because in our shared config it was only used by the github datasource. I am not sure this is needed, though, because the other private dependencies magically have been resolved before adding this.