cowprotocol / cowprotocol/solver-7702-delegate

Enable additional Renovate package managers for this repo

Open
#11 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Solidity
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Context

As part of the org-wide Renovate rollout for GitHub Actions
(announcement),
this repo got a Renovate config in #10 that is deliberately scoped to
GitHub Actions only:

// .github/renovate.json5
enabledManagers: ["github-actions"],

Every other built-in manager (npm, cargo, pip, docker, ...) was disabled during
rollout to avoid flooding repos with project-specific upgrade PRs that teams
didn't opt into.

What to do

The rollout is done — this repo's maintainers now own the Renovate config.
Please review which package managers
are relevant here and enable them, e.g.:

enabledManagers: ["github-actions", "npm"],

Then add packageRules to match how this repo wants updates batched/scheduled
(see the existing github-actions rule in the config as a reference).

If this repo previously used Dependabot for these ecosystems, prefer moving
them into Renovate so we keep one tool and one PR style — but that call is
yours.

Questions / DevOps support: ask in #devops or ping @glokos.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with .github/renovate.json5 and inspect the repository for manifests or configuration that identify relevant package managers. Review the existing GitHub Actions package rule and Renovate's manager documentation, then enable the appropriate managers and add packageRules for the repository's desired batching or scheduling. Done means the config covers the intended ecosystems without retaining unnecessary Dependabot coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, solidity
Domain
devops, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.