Jamie Tanna
d91e6088ff
The `mutation-pr`/`mutation-full` CI jobs were failing outright, and a full `stryker run` never got past the initial dry run, so none of this was actually usable yet. - `mutation.yml`: pin all actions to a commit SHA, add a `permissions` block, set `persist-credentials: false`, and pass the base ref/changed files through `env` instead of interpolating them into the shell script directly (zizmor was flagging all of these). Also switch to the project's own `./.github/actions/setup-node` composite action instead of `pnpm/action-setup`/`actions/setup-node` (which additionally referenced a non-existent `.node-version` file), and fix the `pnpm mutation`/`pnpm stryker run --mutate` calls to use the actual `test:mutation`/`test:mutation:changed` script names. - Drop the now-unused `@stryker-mutator/typescript-checker` dependency, left over from when `stryker.config.json` still had `checkers: ["typescript"]`. - `lib/util/timestamp.ts`: the local-timezone-offset fallback used in `asTimestamp()` was cached in a module-level constant computed once at import time. Combined with vitest's `threads` pool (used by Stryker's vitest-runner) not reliably honouring a `process.env.TZ` set from our own `test/setup.ts`, this made `asTimestamp()` parse plain dates (e.g. Jenkins' `buildDate: 'Jan 02, 2020'`) using the host's real timezone instead of UTC. Compute the offset per call instead, and set `TZ=UTC` in the actual environment via the `test:mutation*` scripts, since that's the one thing that reliably works across pools. - `test/setup.ts`: restore real timers in a top-level `afterAll`, so a spec that leaves fake timers running (there's at least one) can't leak a frozen clock into whichever spec runs next in the same worker - something that's only reachable under low-concurrency/single-threaded execution. - Raise `dryRunTimeoutMinutes` and the global vitest `testTimeout`: our full suite's per-test coverage instrumentation run took ~25 minutes end-to-end, well past Stryker's 5 minute default, and a couple of CPU-heavy specs (WASM PGP crypto) timed out under that contention too. - Ignore `.stryker-tmp/` (Stryker's sandbox dir, which can survive an interrupted run) in ls-lint/oxlint/biome/prettier/vitest, since a leftover sandbox copy of the repo was otherwise picked up as extra source/test files and broke those tools outright. Co-Authored-By: Claude Sonnet 5 <jamie.tanna+claude-code@mend.io>
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.