renovatebot / renovatebot/pre-commit-hooks
(bug) Hook build fails on `pre-commit.ci` due to size limits exceeded
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 49
- Forks
- 10
- Avg merge
- 1m
- Merged PRs (30d)
- 176
Description
Description
My pre-commit.ci run failed during environment initialization after installing this hook with the following error:
build of https://github.com/renovatebot/pre-commit-hooks:renovate@43.216.1@43.216.1 for node@lts exceeds tier max size 250MiB: 610.4MiB
[!WARNING]
I noticed that the build took around 1m and 45s and eventually failed. This is significant because with a warm cache, the build can be around 100ms or 3s when a new hook has been added. When installing the hook locally, it also took a significant time during the environment initialization phase.
Root Cause
The resulting pre-commit environment exceeds the maximum size allowed by pre-commit.ci (250 MiB), causing environment creation to fail before the hook can execute.
This is an incompatibility between:
- The size of the hook's runtime/dependency footprint.
- The environment size limits enforced by
pre-commit.ci.
Impact
For users who rely on pre-commit.ci as their SSOT for CI validation, this integration failure with the target platform makes adoption questionable. This should not be the case given that this is the most developer-convenient option to config validation.
Suggestions
Compatibility with pre-commit.ci should be a goal for this hook, for the community. I believe this is what is being addressed in #4224.
[!NOTE]
Reduce the hook's installation footprint or explore a lighter-weight validation mechanism.
In the meantime, this known limitation with pre-commit.ci should be documented so users avoid running it in CI. This can be accomplished by adding the following to pre-commit-config.yaml:
ci:
...
skip: [renovate-config-validator]
...
Environment
- Hook: renovatebot/pre-commit-hooks
- Hook version: 43.216.1
- Platform: pre-commit.ci
Error:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #4224 and the config-validation documentation linked in the report, then inspect how the renovate-config-validator hook is built for node@lts. Done means either documenting the pre-commit.ci 250 MiB limitation and the skip configuration, or demonstrating that the hook installs and runs within the platform limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100