mirror of
https://github.com/renovatebot/renovate.git
synced 2026-10-26 07:20:39 +00:00
y.takahashi
ff0e5eed24
* feat(npm): extract devEngines.runtime and devEngines.packageManager Adds extraction for the npm devEngines field (https://docs.npmjs.com/cli/v11/configuring-npm/package-json#devengines) covering both single-object and array forms. Uses dot-notated depTypes ("devEngines.runtime", "devEngines.packageManager") consistent with "pnpm.overrides", and reuses the existing engines/packageManager datasource resolution. Items without a version are skipped. Refs #38067. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(npm): update devEngines.runtime and devEngines.packageManager versions Adds an update path for the new devEngines depTypes. Handles both the single-object form and the array form (the array element is identified via managerData.devEnginesIndex set at extraction time). Uses the same anchored search-and-verify approach as the existing replaceAsString (indexOf("devEngines") + dequal check), so unrelated occurrences of the same version string elsewhere in the file are not touched. Refs #38067. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(npm): skip lockedVersion and apply @yarnpkg/cli for devEngines deps Extends the locked-versions post-extract step to cover the new devEngines depTypes: - devEngines.runtime and devEngines.packageManager are added to the npm-lock skip list (mirrors the engines/packageManager/volta handling added in #38598) - devEngines.packageManager with depName "yarn" gets the @yarnpkg/cli packageName fallback when the project is on Yarn 2+, matching the existing behavior for engines / packageManager Refs #38067. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(npm): harden devEngines handling against malformed input - Register devEngines.runtime and devEngines.packageManager in knownDepTypes (matches the existing pnpm.overrides pattern) - Guard against null/non-object array elements in devEngines.* during extraction so malformed JSON does not throw - Use JSON.stringify when interpolating versions into the source search string, so any future versions containing JSON-escaped characters are matched correctly - Add an extraction test for a mixed array containing a null item, a valid entry, and a version-less entry Refs #38067. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(npm): set hasPackageManager when devEngines.packageManager is an array The previous hasPackageManager check used isNonEmptyObject which returns false for arrays. Now that the array form of devEngines.packageManager is actually extractable and updatable, the corepack post-update step needs to be triggered for those users as well. Introduces a shared hasDevEnginesPackageManager helper and uses it from both extractPackageJson and extractPackageFile. Refs #38067. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(npm): require at least one non-empty array item for hasPackageManager Align the array branch of hasDevEnginesPackageManager with the single-object branch by requiring at least one non-empty object item. Previously, an array containing only null/empty entries would set hasPackageManager to true and trigger corepack post-update even though no usable item exists. Add coverage for the empty-array and only-invalid-items cases. Refs #38067. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * test(npm): document hasPackageManager semantics for stray-key array items Make the chosen semantic explicit: an array element with arbitrary keys but no `name` (e.g. `[{ foo: 'bar' }]`) still sets hasPackageManager to true, mirroring the pre-existing single-object behavior. The extract step independently filters out items lacking `name`/`version`. Refs #38067. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * test(npm): cover dequal rejection in devEngines array update Adds a test where two devEngines.packageManager array items share the same version string. The first source-level match belongs to the wrong index, so the dequal verification rejects it and the loop continues to the correct occurrence. This exercises the false branch of the dequal check in updateDevEnginesDependency. Refs #38067. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(node): list devEngines.runtime as a supported field for Node.js The npm manager now updates the version inside devEngines.runtime in package.json, so include it in the file-support list alongside engines and volta. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * Apply the comment changes suggested in the code review Co-authored-by: Michael Kriese <michael.kriese@gmx.de> * test(npm): cover devEngines update error path instead of ignoring it Remove the v8 ignore on the updateDevEnginesDependency catch and add a test that reaches it with invalid JSON, matching how the main updateDependency catch is covered. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(npm): drop unnecessary spread fallback in devEngines managerData Object spread ignores null/undefined, so the `?? {}` fallback is redundant. Removing it satisfies the oxlint no-unnecessary-spread-fallback rule that now runs in CI. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * refactor(npm): type devEnginesIndex on NpmManagerData Declare devEnginesIndex on NpmManagerData so the value no longer needs a `as number | undefined` cast when reading it back during update. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(node): document package manager version fields List packageManager and devEngines.packageManager separately from the Node.js runtime file support entries. Co-authored-by: Codex <noreply@openai.com> * feat(npm): support Bun and Deno devEngines runtimes * fix(npm): preserve Corepack hashes in devEngines * test(npm): use partial helper for devEngines fixture Co-authored-by: Codex <noreply@openai.com> * fix(npm): warn on invalid devEngines update state Co-authored-by: Codex <noreply@openai.com> * fix(npm): include devEngines in extracted tool constraints Co-authored-by: Codex <noreply@openai.com> * fix(npm): prefer devEngines over volta for package manager versions Co-authored-by: Codex <noreply@openai.com> * fix(npm): update Yarn binaries for devEngines package manager upgrades Co-authored-by: Codex <noreply@openai.com> * fix(npm): recognize devEngines package managers for Yarn catalogs Co-authored-by: Codex <noreply@openai.com> * fix(npm): exclude devEngines from Yarn locked versions Co-authored-by: Codex <noreply@openai.com> * refactor(npm): reuse Bun extraction for devEngines runtime Co-authored-by: Codex <noreply@openai.com> * test(npm): cover Yarn devEngines manifest preservation and grouped updates Co-authored-by: Codex <noreply@openai.com> * refactor(npm): pass packageJsonResult directly to hasDevEnginesPackageManager Co-authored-by: Michael Kriese <michael.kriese@gmx.de> * test(npm): simplify malformed devEngines fixture Co-authored-by: Codex <noreply@openai.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Michael Kriese <michael.kriese@gmx.de> Co-authored-by: Codex <noreply@openai.com>
What is the Mend Renovate CLI?
Renovate is an automated dependency update tool. It helps to update dependencies in your code without needing to do it manually. When Renovate runs on your repo, it looks for references to dependencies (both public and private) and, if there are newer versions available, Renovate can create pull requests to update your versions automatically.
Features
- Delivers update PRs directly to your repo
- Relevant package files are discovered automatically
- Pull Requests automatically generated in your repo
- Provides useful information to help you decide which updates to accept (age, adoption, pass rates, merge confidence)
- Highly configurable and flexible to fit in with your needs and repository standards
- Largest collection of languages and platforms (listed below)
- Connects with private repositories and package registries
Languages
Renovate can provide updates for most popular languages, platforms, and registries including: npm, Java, Python, .NET, Scala, Ruby, Go, Docker and more. Supports over 90 different package managers.
Platforms
Renovate updates code repositories on the following platforms: GitHub, GitLab, Bitbucket, Azure DevOps, AWS Code Commit (experimental), Gitea, Forgejo, Gerrit (experimental), SCM-Manager (experimental)
Ways to run Renovate
The most effective way to run Renovate is to use an automated job scheduling system that regularly runs Renovate on all enabled repositories and responds with priority to user activity. Mend offers cloud-hosted and self-hosted solutions. See the options below.
Mend Renovate Community (Cloud-Hosted)
Supports: GitHub.com, Bitbucket Cloud
Hosted by Mend.io. No setup is needed. Community plan available (Free)
- GitHub Cloud: Install the Renovate Cloud-Hosted App on your GitHub org, then select the repos to enable
- Bitbucket Cloud: Add the Mend App to your Workspace, then add the Mend Renovate user to the projects you want to enable
Mend Renovate Community (Self-hosted)
Supports: GitHub, GitLab, Bitbucket Data Center
Install and run your own Renovate server. Access internal packages.
- Mend Renovate Community Self-Hosted (Free)
- Mend Renovate Enterprise (Paid plan)
Other ways to run Renovate
If you can’t use a pre-built job scheduling system, or want to build your own, the following options are available:
Run Renovate on your Pipeline
Mend provides a GitHub Action or a GitLab Runner to help you run Renovate as a CI pipeline job.
- GitHub Action: renovatebot/github-action.
- GitLab Runner: Renovate Runner project
- AzureDevOps action: Renovate Me extension
Note: This extension is created and maintained personally by a Renovate developer/user. Support requests for the extension will not be answered directly in the main Renovate repository. - Custom pipeline: You can create a custom pipeline with a yml definition that triggers npx renovate. More details on how to configure the pipeline.
Run Renovate CLI
There are several ways to run the Renovate CLI directly. See docs: Running Renovate for all options.
Supports: all platforms
For additional community-maintained options, see the Community Tools page.
Docs
More about Renovate
- Renovate basics
- Supported platforms and languages
- Advanced Renovate usage
Renovate Docs
Comparisons
Get involved
Issues and Discussions
Please open a Discussion to get help, suggest a new feature, or to report a bug. We only want maintainers to open Issues.
Contributing
To contribute to Renovate, or run a local copy, please read the contributing guidelines.
- Guidelines for Contributing
- Items that need contribution: good first issues
Contact and Social Media
The Renovate project is proudly supported and actively maintained by Mend.io.
- Contact Mend.io for commercial support questions.
Follow us on:
- Twitter: x.com/mend_io
- LinkedIn: linkedin.com/company/mend-io
Security / Disclosure
If you find any bug with Renovate that may be a security problem, please report it through the GitHub Security Advisories process. This way we can evaluate the bug and hopefully fix it before it gets abused. Please give us enough time to investigate the bug before you report it anywhere else.
If you would like to discuss a potential finding before raising the Advisory, then e-mail us at: renovate-disclosure@mend.io.