Can't get Renovate to work for yarn v3 monorepo using gh npm private registry and fontawesome registry

[marcossv9]

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'm trying to configure Renovate app in github.com for a monorepo using [email protected].

The monorepo uses npm packages from:

• npm public registry
• github npm private registry.
• fontawesome npm registry

we don't have .npmrc file, we uses yarnrc.yaml where we have set up fontawesome registry like this:

npmRegistries:
  //npm.fontawesome.com/:
    npmAuthToken: <REDACTED_TOKEN>

npmScopes:
  fortawesome:
    npmRegistryServer: "https://npm.fontawesome.com/"

So following the mixed up documentation about yarn v3 monorepo and usage of private registry, we end up with this renovate.json config:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "automerge": false,
  "extends": [
    "config:recommended"
  ],
  "enabledManagers": [
    "npm"
  ],
  "packageRules": [
    {
      "extends": [
        "monorepo:yarn"
      ],
      "groupName": "yarn monorepo",
      "matchSourceUrls": [
        "https://github.com/yarnpkg/berry"
      ],
      "matchUpdateTypes": [
        "digest",
        "patch",
        "minor"
      ]
    }
  ],
  "prConcurrentLimit": 1,
  "rebaseWhen": "conflicted"
}

NOTE: host rules and secrets are configured inside https://developer.mend.io/github/MY_ORG/MY_REPO/-/settings like so:

Error we see in the developer portal:

What am I doing wrong here?

Any help would be appreciated, thanks!

Logs (if relevant)

For some reason, renovate default to registry.npmjs.org for private packages and for fontawesome packages.

DEBUG: Adding token authentication for https://npm.fontawesome.com/ (hostType=npm) to hostRules
DEBUG: Adding token authentication for https://npm.pkg.github.com/ (hostType=npm) to hostRules


GET https://registry.npmjs.org/@my-org%2Fmy-private-package = (code=ERR_NON_2XX_3XX_RESPONSE, statusCode=404 retryCount=0, duration=957)
DEBUG: Failed to look up npm package @my-org/my-private-package
DEBUG: Failed to look up npm package @fortawesome/pro-regular-svg-icons
DEBUG: GET https://registry.npmjs.org/@fortawesome%2Fpro-light-svg-icons = (code=ERR_NON_2XX_3XX_RESPONSE, statusCode=404 retryCount=0, duration=4339)

So obviously it returns 404 cuz they are not in that registry.

[marcossv9]

I have managed to fix this 404 issue by not using the mend hosted app, but instead running the renovate gh action as self-hosted inside a scheduled gh workflow.
Now working some kinks with updating the lock file in renovate PRs using yarn 3.5.1.

[marcossv9]

for those curious, this is my config.js:

module.exports = {
  $schema: 'https://docs.renovatebot.com/renovate-schema.json',
  autodiscover: true,
  autodiscoverFilter: ['GithubOrg/my-repo'],
  automerge: false,
  extends: [
    'config:recommended'
  ],
  enabledManagers: [
    'npm'
  ],
  hostRules: [
    {
      matchHost: 'https://npm.pkg.github.com/',
      hostType: 'npm',
      token: process.env.RENOVATE_GH_PRIVATE_PACKAGES_TOKEN,
    },
    {
      matchHost: 'https://npm.fontawesome.com/',
      hostType: 'npm',
      token: process.env.RENOVATE_FONTAWESOME_NPM_TOKEN,
    },
  ],
  labels: [
    'dependencies'
  ],
  npmrc: '@fortawesome:registry=https://npm.fontawesome.com\n@GithubOrg:registry=https://npm.pkg.github.com',
  onboarding: false,
  packageRules: [
    {
      'extends': [
        'monorepo:yarn'
      ],
      'groupName': 'yarn monorepo',
      'matchSourceUrls': [
        'https://github.com/yarnpkg/berry'
      ],
      'matchUpdateTypes': [
        'digest',
        'patch',
        'minor',
      ]
    }
  ],
  platform: 'github',
  // platform: 'local',
  prConcurrentLimit: 1,
  rebaseWhen: 'never',
  requireConfig: 'optional',
  repositories: ['GithubOrg/my-repo'],
  repositoryCache: 'enabled',
  semanticCommits: 'enabled',
};