Delegation hint — this is a mechanical edit. If you need a sub-agent for the pin change, use version-bumper (haiku). The build step at the end can be delegated to build-runner (haiku).

Steps:

Search megalinter/descriptors/*.megalinter-descriptor.yml for the linter by name
Find the version ARG in the install.dockerfile section (e.g., ARG PIP_TOOL_VERSION=X.Y.Z) or version pin in pip/npm arrays

Update the version, preserving the renovate comment format:

# renovate: datasource=pypi depName=tool-name
ARG PIP_TOOL_VERSION=<new_version>

If no version was specified, check the tool's package registry for the latest
Run make megalinter-build to regenerate Dockerfiles with the new version
Do not update CHANGELOG.md — linter version upgrades are logged automatically by the auto-upgrade workflow under Linter versions upgrades
To test the updated version in CI, write TEST_KEYWORDS=<linter>_test in the commit message body

Más de este repositorio

mismo repositorio

pr-watch-fix-renovate

oxsecurity/megalinter

Run the pr-watch-fix loop in parallel across every open Renovate-bot PR, each in its own git worktree. Use to green-light or triage all dependency-update PRs at once.

2026-07-052.5k

fix-security-issue

oxsecurity/megalinter

Handle CVE/vulnerability reports from security linters (trivy, osv-scanner, etc.). Tries to upgrade first; ignores only when safe and justified; disables an unmaintained linter (with user confirmation) when a dangerous CVE has no fix.

2026-07-052.5k

pr-watch-fix

oxsecurity/megalinter

Watch the GitHub PR for the current branch, wait for CI to finish, and autonomously fix failing jobs by reading logs, editing sources, and pushing. Stops cleanly when stuck.

2026-07-052.5k

prepare-release

oxsecurity/megalinter

Prepare a MegaLinter release — update CHANGELOG (prune empty sections, collapse linter versions, backfill PR numbers), run the release build, push commit and tag, and guide GitHub release creation.

2026-06-282.5k

add-flavor

oxsecurity/megalinter

Add a new MegaLinter flavor (language-specific Docker image). Use when creating a new specialized Docker image variant.

2026-05-242.5k

add-linter

oxsecurity/megalinter

Guided workflow for adding a new linter to MegaLinter. Use when a contributor needs to add support for a new linting tool.

2026-05-242.5k

name	update-linter-version
description	Update a linter's pinned version in its descriptor YAML. Use when upgrading a linter tool to a new release.

Update the version of linter $linter to $version.

Delegation hint — this is a mechanical edit. If you need a sub-agent for the pin change, use version-bumper (haiku). The build step at the end can be delegated to build-runner (haiku).

Steps:

Search megalinter/descriptors/*.megalinter-descriptor.yml for the linter by name
Find the version ARG in the install.dockerfile section (e.g., ARG PIP_TOOL_VERSION=X.Y.Z) or version pin in pip/npm arrays

Update the version, preserving the renovate comment format:

# renovate: datasource=pypi depName=tool-name
ARG PIP_TOOL_VERSION=<new_version>

If no version was specified, check the tool's package registry for the latest
Run make megalinter-build to regenerate Dockerfiles with the new version
Do not update CHANGELOG.md — linter version upgrades are logged automatically by the auto-upgrade workflow under Linter versions upgrades
To test the updated version in CI, write TEST_KEYWORDS=<linter>_test in the commit message body