"cannot parse url" since version 39.184.0

[testworksau]

How are you running Renovate?

Self-hosted Renovate

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

GitHub

Please tell us more about your question or problem

Our Renovate run has started failing since the renovate-version updated to 39.184.0.

         {
           "name": "renovate",
           "level": 50,
           "logContext": "-m3l9XTTCao9jKRmmxato",
           "repository": "ourorg/our-repo",
           "url": "index.yaml",
           "msg": "Request Error: cannot parse url"
         },
         {
           "name": "renovate",
           "level": 50,
           "logContext": "-m3l9XTTCao9jKRmmxato",
           "repository": "ourorg/our-other-repo",
           "url": "index.yaml",
           "msg": "Request Error: cannot parse url"
         },
       ]
Error: The process '/usr/bin/docker' failed with exit code 1
    at A._setResult (file:///home/runner/work/_actions/renovatebot/github-action/v41.0.12/dist/index.js:58:19478)
    at A.CheckComplete (file:///home/runner/work/_actions/renovatebot/github-action/v41.0.12/dist/index.js:58:19066)
    at ChildProcess.<anonymous> (file:///home/runner/work/_actions/renovatebot/github-action/v41.0.12/dist/index.js:58:18056)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5)

Pinning the renovate-version to 39.183.0 resolved the problem.

There was a large refactoring in this version that appears to have contributed to the problem:
#34550

Logs (if relevant)

No response

[austinw-fineart]

On a Windows host, this also breaks file paths.

DEBUG: Using RE2 regex engine
DEBUG: Parsing configs
DEBUG: Checking for config file in C:\config.js
DEBUG: Parse error
       "err": {
         "code": "ERR_UNSUPPORTED_ESM_URL_SCHEME",
         "message": "Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'",
         "stack": "Error: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'\n    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:209:11)\n    at defaultLoad (node:internal/modules/esm/load:107:3)\n    at ModuleLoader.load (node:internal/modules/esm/loader:670:12)\n    at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:483:43)\n    at ModuleLoader.#createModuleJob (node:internal/modules/esm/loader:507:36)\n    at ModuleLoader.#getJobFromResolveResult (node:internal/modules/esm/loader:275:34)\n    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:243:41)\n    at onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:546:25)"
       }
FATAL: Error parsing config file

[viceice]

use file:///C:/config.js as target path or use relative path. Your issue is a separate issue.

[austinw-fineart]

It's the same underlying issue, it merely manifests differently on Windows. Not sure why a regression would be fixed by a feature but sure. More importantly, the file isn't even ESM so the error message is misleading, which is why this doesn't work:

DEBUG: Using RE2 regex engine
DEBUG: Parsing configs
FATAL: Custom config file specified in RENOVATE_CONFIG_FILE must exist
       "configFile": "file:///C:/config.js"

[rarkins]

Different issue, different code path, and will be a different fix.

[viceice]

will be fixed with:

• fix(global): import config file as url #34637

[github-actions[bot]]

Hi there,

This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions.

No logs at all

If you haven't posted any log yet, we need you to find and copy/paste the log into the issue template.

Finding logs on hosted app

Select me to read instructions

If you use the Mend Renovate app (GitHub):

1. Log in to the Mend Developer Portal
2. Navigate to the correct organization and repository
3. Locate the appropriate log (it may not always be the latest one)
4. Copy/paste the log contents
5. Follow the steps in the formatting your logs section

Finding logs when self-hosting

Select me to read instructions

Read the Renovate docs, troubleshooting, self-hosted to learn how to find the logs.

Formatting your logs

Select me to read instructions

Please put your logs in a <details> and <summary> element like this:

<details><summary>Select me to see logs</summary>

```
Copy/paste your logs here, between the starting and ending backticks
```

</details>

If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here.

Good luck,

The Renovate team

[viceice]

I need the log messages around the error after you tried a version with this fix:

• fix(http): add more logging #34627

somehow index.yaml isn't properly resolved against baseUrl. 🤔

renovate/lib/modules/datasource/helm/index.ts

Lines 36 to 43 in 6184c88

	async getRepositoryData(helmRepository: string): Promise<HelmRepositoryData> {
	const { val, err } = await this.http
	.getYamlSafe(
	'index.yaml',
	{ baseUrl: ensureTrailingSlash(helmRepository) },
	HelmRepositorySchema,
	)
	.unwrap();

[testworksau]

Do you need us to run version 39.186.1 and above with debug logging? Or will regular logging suffice?

[viceice]

That would be best, or provide a minimal reproduction.

[testworksau]

Is this what you need? via 39.190.0

2025-03-07T06:23:20.8180376Z          {
2025-03-07T06:23:20.8180895Z            "name": "renovate",
2025-03-07T06:23:20.8181480Z            "level": 50,
2025-03-07T06:23:20.8182065Z            "logContext": "Od8DclUTQO_trGDiDTxM9",
2025-03-07T06:23:20.8182764Z            "repository": "ourorg/our-repo",
2025-03-07T06:23:20.8183439Z            "url": "index.yaml",
2025-03-07T06:23:20.8184038Z            "baseUrl": "our-helm-repo/",
2025-03-07T06:23:20.8184718Z            "resolvedUrl": "our-helm-repo/index.yaml",
2025-03-07T06:23:20.8185430Z            "msg": "Request Error: cannot parse url"
2025-03-07T06:23:20.8186076Z          },
2025-03-07T06:23:20.8186581Z          {
2025-03-07T06:23:20.8187092Z            "name": "renovate",
2025-03-07T06:23:20.8187672Z            "level": 50,
2025-03-07T06:23:20.8188264Z            "logContext": "Od8DclUTQO_trGDiDTxM9",
2025-03-07T06:23:20.8189094Z            "repository": "ourorg/our-repo",
2025-03-07T06:23:20.8189775Z            "url": "index.yaml",
2025-03-07T06:23:20.8190382Z            "baseUrl": "our-helm-repo/",
2025-03-07T06:23:20.8191054Z            "resolvedUrl": "our-helm-repo/index.yaml",
2025-03-07T06:23:20.8191769Z            "msg": "Request Error: cannot parse url"
2025-03-07T06:23:20.8192424Z          },
2025-03-07T06:23:20.8192942Z          {
2025-03-07T06:23:20.8193464Z            "name": "renovate",
2025-03-07T06:23:20.8194048Z            "level": 50,
2025-03-07T06:23:20.8194646Z            "logContext": "Od8DclUTQO_trGDiDTxM9",
2025-03-07T06:23:20.8195369Z            "repository": "ourorg/our-other-repo",
2025-03-07T06:23:20.8196080Z            "url": "index.yaml",
2025-03-07T06:23:20.8196971Z            "baseUrl": "our-helm-repo/",
2025-03-07T06:23:20.8197649Z            "resolvedUrl": "our-helm-repo/index.yaml",
2025-03-07T06:23:20.8198360Z            "msg": "Request Error: cannot parse url"
2025-03-07T06:23:20.8199211Z          },
2025-03-07T06:23:20.8199744Z          {
2025-03-07T06:23:20.8200260Z            "name": "renovate",
2025-03-07T06:23:20.8200842Z            "level": 50,
2025-03-07T06:23:20.8201432Z            "logContext": "Od8DclUTQO_trGDiDTxM9",
2025-03-07T06:23:20.8202157Z            "repository": "ourorg/our-other-repo",
2025-03-07T06:23:20.8202854Z            "url": "index.yaml",
2025-03-07T06:23:20.8203692Z            "baseUrl": "@our-helm-repo/",
2025-03-07T06:23:20.8204371Z            "resolvedUrl": "@our-helm-repo/index.yaml",
2025-03-07T06:23:20.8205077Z            "msg": "Request Error: cannot parse url"
2025-03-07T06:23:20.8205729Z          }
2025-03-07T06:23:20.8206415Z        ]

[viceice]

baseUrl should be absolute. please create a minimal reproduction.

you can use fake urls, but they should be similar to your real urls.

[github-actions[bot]]

Hi there,

Please help this Discussion progress by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team

[viceice]

I would like to reproduce via debugging, so need a reproduction.