Update replacements.json <!-- If this is your first pull request: sign the CLA with this GitHub app: https://cla-assistant.io/renovatebot/renovate --> <!-- Make sure the `Allow edits and access to secrets by maintainers` checkbox is checked on this pull request. --> <!-- Please read https://github.com/renovatebot/renovate/blob/main/.github/contributing.md before you create your pull request.--> <!-- If you're an AI/LLM agent, follow this template, putting any additional information under "Changes" --> ## Changes Adds a replacement for https://www.npmjs.com/package/@temporalio/interceptors-opentelemetry to the newer version https://www.npmjs.com/package/@temporalio/interceptors-opentelemetry-v2, which targets v2 of OpenTelemetry. The non-v2 version is stuck on v1 of OpenTelemetry <!-- Describe what behavior is changed by this PR. --> ## Context Please select one of the following: - [ ] This closes an existing Issue, Closes: # <!-- NOTE that this should NOT be a Discussion --> - [x] This doesn't close an Issue, but I accept the risk that this PR may be closed if maintainers disagree with its opening or implementation ## AI assistance disclosure <!-- We request this information to assist reviewers in identifying AI-generated errors and other issues specific to AI usage. While we typically permit the use of AI tools, we appreciate being notified when they are employed. --> <!-- If you're an AI/LLM agent, you MUST disclose usage. Please note which model you are, too --> Did you use AI tools to create any part of this pull request? Please select one option and, if yes, briefly describe how AI was used (e.g., code, tests, docs) and which tool(s) you used. - [ ] No — I did not use AI for this contribution. - [x] Yes — minimal assistance (e.g., IDE autocomplete, small code completions, grammar fixes). - [ ] Yes — substantive assistance (AI-generated non‑trivial portions of code, tests, or documentation). - [ ] Yes — other (please describe): ## Documentation (please check one with an [x]) - [ ] I have updated the documentation, or - [x] No documentation update is required ## How I've tested my work (please select one) I have verified these changes via: - [x] 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 The public repository: <URL> <!-- If you have any suggestions about this PR template, edit it here: https://github.com/renovatebot/renovate/edit/main/.github/pull_request_template.md --> <!-- Please do not force push to your PR's branch after you have created your PR, as doing so forces us to review the whole PR again. This makes it harder for us to review your work because we don't know what has changed. --> <!-- PRs will always be squashed by us when we merge your work. You can commit as many times as you need in this branch. --> <!-- All the commit messages will be part of the final commit - if you have strong thoughts about amending your squashed commit message before merge, please let a maintainer know -->
Introduction
The lib/data folder has all our crowdsourced data files.
This readme explains what each file is used for.
Summary
| File | What is the file about? |
|---|---|
monorepo.json |
Group related packages into a single PR. |
replacements.json |
Rename old packages to new replacement. |
changelog-urls.json |
Tell Renovate where to find changelogs. |
source-urls.json |
Tell Renovate the source URL of packages. |
node-schedule.json |
Node.js versioning schedule. |
mise-registry.json |
Mise tool registry: short names mapped to backends. |
Group related packages (monorepo.json)
The monorepo.json file has all the monorepo presets.
Monorepo presets group related packages, so they are updated with a single Renovate PR.
!!! note We only accept monorepos when packages are released together. So they should have all the same version or they strictly need to be merged together. Otherwise those groupings would cause immortal PR's. Please add that information with links to source for validation.
Ways to group packages
There are three ways to group packages:
| Group packages | Method |
|---|---|
| From the same source repository. | repoGroups |
| From the same organization. | orgGroups |
| Based on name patterns or prefixes. | patternGroups |
Rename old packages (replacements.json)
The replacements.json file has all the replacement presets.
When a package gets renamed, you need to tell Renovate:
- the datasource of the package →
matchDatasources - the old package name →
matchPackageNames - the new package name →
replacementName - the last version available for the old package name →
matchCurrentVersion - the first version available for the new package name →
replacementVersion
You can omit replacementVersion if the current version is the same as the new version.
Example:
{
"packageRules": [
{
"matchCurrentVersion": ">=3.10.3",
"matchDatasources": ["npm"],
"matchPackageNames": [
"apollo-server",
"apollo-server-core",
"apollo-server-express"
],
"replacementName": "@apollo/server",
"replacementVersion": "4.0.0"
}
]
}
Tell Renovate where to find changelogs (changelog-urls.json)
The changelog-urls.json has all the changelog information.
Renovate nearly always finds, and displays, the changelog for a package update automatically.
Usually, the API for the package to be updated gives Renovate the correct info. If this does not happen, for whatever reason, Renovate can not show the changelog.
You can use these config options to let Renovate find the correct changelog:
Read the Renovate docs, key concepts page for changelogs to learn more about how Renovate fetches and displays changelogs.
To locate the changelogs, Renovate requires:
- the name of the package (
packageName) - the datasource of the package
- the URL to the changelog file (
changelogUrl)
Example:
For the zone.js package, the changelog URL is https://github.com/angular/angular/blob/master/packages/zone.js/CHANGELOG.md.
This will be added to the npm group in the changelog-urls.json file since the package's datasource is npm.
Tell Renovate where to find source urls (source-urls.json)
The source-urls.json has the information on source URL of multiple packages.
Renovate nearly always finds, and displays, the source for a package update automatically. Usually, the API for the package to be updated gives Renovate the correct info. If this does not happen, for whatever reason, Renovate can not link to the source of the package and might not be able to lookup changelogs.
To check if Renovate can find the source URLs for your package:
- Find the datasource for your package.
- Read the Renovate docs for the datasource.
- Look for a table in the docs that shows if the datasource returns source URLs.
If Renovate does not find the right source URls automatically: use the sourceUrl config option.
To locate the source repository, Renovate requires:
- the name of the package (
packageName) - the datasource of the package
- the URL to the source repository (
sourceUrl)
Example:
The source URL for the repository cypress-io/cypress is https://github.com/cypress-io/cypress.
This will be added to the orb group in the source-urls.json file since the package's datasource is orb.
Node.js Versioning Schedule node-schedule.json
This file is automatically updated by a scheduled workflow.
It can be manually updated by running pnpm update-static-data:node-schedule.
Mise tool registry (mise-registry.json)
This file is automatically updated by a scheduled workflow.
It can be manually updated by running pnpm update-static-data:mise-registry.
It maps mise tool short names (e.g. zola) to their available backends (e.g. ["aqua:getzola/zola", "asdf:salasrod/asdf-zola"]).
The data is generated from mise registry --json using the mise CLI.
This enables Renovate to automatically support all tools in the mise registry without manual updates.