Emanuel Besliu
483890a8f1
* fix(platform/azure): resolve work item states from process Renovate hardcoded the Azure Boards work item state to `New` on create/reopen and `Closed` on close. Processes that don't have those states (Basic uses To Do/Done; custom inherited processes vary) reject the request with "The field 'State' contains the value 'New' that is not in the list of supported values", so the Dependency Dashboard (and any issue) could not be created or closed. Resolve the concrete open/closed state names for the `Issue` work item type from its process via `getWorkItemTypeStates`, grouped by state category (Proposed/InProgress = open, Completed/Resolved/Removed = closed). Omit `System.State` on create so Azure DevOps applies the work item type's default initial state. Classify issues open/closed by state category rather than the literal `Closed`. Fall back to the previous `New`/`Closed` names when the states cannot be read (e.g. older ADO Server). Result is cached per repository. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(platform/azure): prefer Completed state as close target Address review: closedNames[0] picked the first state across the Completed/Resolved/Removed categories in workflow order, so processes that order a Resolved-category state before the Completed one (e.g. a custom inherited Agile process) would close work items to `Resolved` instead of `Closed`, changing prior behavior. Resolve the close target from the `Completed` category first, falling back to the wider closed set only when no Completed state exists. The full closed set is still used to classify already-closed items. Add tests covering a process where `Resolved` is ordered before `Closed`. * fix(platform/azure): address review feedback on state resolution - Extract namesByCategory into a module-level function declaration instead of an arrow function assigned to a variable. - Add a test where the Issue type exposes a closed-category state but no Completed state, exercising the completedNames[0] ?? closedNames[0] fallback (restores 100% patch coverage). - Reword the readme to avoid possessives per the style guide. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * refactor(platform/azure): simplify state resolution per review - use stateColors.find for the Completed close target instead of an extra namesByCategory pass over a single-element array - document that the open-state fallback may pick a closed state when a process exposes only closed states (intentional, not a bug) - reuse the workItemType const instead of repeating the 'Issue' literal Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(platform/azure): resolve work item states via Lazy getWorkItemStates was async with a plain null-check cache guard, so two concurrent callers could both pass the guard and each fire a duplicate getWorkItemTypeStates request. Wrap resolution in `Lazy<Promise<...>>` so the executor runs once and all callers share the same promise. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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.