👷 fix renovate config and integration app yarn version#112
Merged
Conversation
The previous matchRegistryUrls rule didn't fire because Renovate's docker datasource extracts the registry as part of the package name, not as a separate registryUrl. Switch to matchDatasources + matchPackageNames glob so renovate stops trying to look up registry.ddbuild.io/images/docker and registry.ddbuild.io/slack-notifier.
Without an explicit packageManager field, each integration app inherited yarn@4.12.0 via directory walk-up to the root package.json. Renovate's runner then fell back to global yarn 1 and refused to install. Making each app self-describing lets Renovate (with corepack) resolve the correct yarn version.
bcaudan
added a commit
that referenced
this pull request
May 4, 2026
These two subprojects also have their own yarn.lock and were missing the packageManager field, so Renovate's runner fell back to global yarn 1 when trying to update their lockfiles. Mirroring the fix from #112 for the integration apps.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Address two warnings reported on the recent Renovate setup:
registry.ddbuild.io/images/dockerandregistry.ddbuild.io/slack-notifier.e2e/integration/apps/forge-vitefailed because the runner's global yarn 1 refused to install in a project declaring yarn 4.Changes
matchRegistryUrlsignore rule withmatchDatasources: ["docker"]+matchPackageNames: ["registry.ddbuild.io/**"]. The previous rule never matched because Renovate's docker datasource embeds the registry in the package name rather than a separateregistryUrl, so lookups against the internal registry kept failing."packageManager": "yarn@4.12.0"to each integration app'spackage.json(forge-vite,forge-webpack,electron-vite,electron-builder-vite). Without it the apps inherited the root'spackageManagervia directory walk-up, but the Renovate runner fell back to global yarn 1. Making each app self-describing lets the runner (with corepack) resolve the correct yarn.Test instructions
Config-only change; verification happens on the next scheduled Renovate run. After this lands:
registry.ddbuild.io/...lookup failures.Checklist
N/A, config-only