Skip to content

Configure Renovate #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

anaconda-renovate[bot]
Copy link

@anaconda-renovate anaconda-renovate bot commented Oct 16, 2023

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • .github/workflows/check-release.yml (github-actions)
  • .github/workflows/docs.yml (github-actions)
  • .github/workflows/enforce-label.yml (github-actions)
  • .github/workflows/js.yml (github-actions)
  • .github/workflows/lock.yml (github-actions)
  • .github/workflows/python-nbconvert.yml (github-actions)
  • .github/workflows/python.yml (github-actions)
  • .github/workflows/selenium.yml (github-actions)
  • package.json (npm)
  • pyproject.toml (pep621)
  • docs/doc-requirements.txt (pip_requirements)
  • setup.py (pip_setup)
  • renovate.json (renovate-config-presets)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Pin Docker digests.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Convert pinned GitHub Action digests to SemVer.
  • Use node versioning for @types/node.
  • Use specific versioning for Red Hat-maintained container images.
  • Update _VERSION variables in Dockerfiles.
  • Update _VERSION environment variables in GitHub Action files.
  • Use the Anaconda Best Practice configuration from anaconda/renovate-config
  • Create a Dependency Dashboard as Issue, listing all upgrades
  • Open new PRs automatically every weekday before 6am UTC. You can manually trigger PRs from the Dependency Dashboard, those will be opened once renovate runs again (once every hour)
  • Label all PRs with renovate
  • Use semantic commit messages for all upgrades
  • Open a maximum of 10 PRs concurrently
  • Automatically set reviewers from CODEOWNERS
  • Upgrade arbitrary dependencies in Dockerfiles when you mark them, see the documentation for details
  • Run Renovate on following schedule: every weekday

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


What to Expect

With your current configuration, Renovate will create 24 Pull Requests:

chore(deps): pin dependencies
chore(deps): update r-lib/actions action to v1.0.2
  • Schedule: ["every weekday"]
  • Branch name: renovate/r-lib-actions-1.x
  • Merge into: master
  • Upgrade r-lib/actions to f5b3dfbf1942ce68283de21bf65cce051e3a2c4d
chore(deps): update actions/cache action to v1.2.1
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-cache-1.x
  • Merge into: master
  • Upgrade actions/cache to f5ce41475b483ad7581884324a6eca9f48f8dcc7
chore(deps): update actions/cache action to v2.1.8
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-cache-2.x
  • Merge into: master
  • Upgrade actions/cache to 2b250bc32ad02700b996b496c14ac8c2840a2991
chore(deps): update actions/checkout action to v1.2.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-checkout-1.x
  • Merge into: master
  • Upgrade actions/checkout to 50fbc622fc4ef5163becd7fab6573eac35f8462e
chore(deps): update actions/checkout action to v2.7.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-checkout-2.x
  • Merge into: master
  • Upgrade actions/checkout to ee0669bd1cc54295c223e0bb666b733df41de1c5
chore(deps): update actions/setup-node action to v1.4.6
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-setup-node-1.x
  • Merge into: master
  • Upgrade actions/setup-node to f1f314fca9dfce2769ece7d933488f076716723e
chore(deps): update actions/setup-node action to v2.5.2
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-setup-node-2.x
  • Merge into: master
  • Upgrade actions/setup-node to 7c12f8017d5436eb855f1ed4399f037a36fbd9e8
chore(deps): update actions/setup-python action to v1.2.4
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-setup-python-1.x
  • Merge into: master
  • Upgrade actions/setup-python to 0f07f7f756721ebd886c2462646a35f78a8bc4de
chore(deps): update actions/setup-python action to v2.3.4
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-setup-python-2.x
  • Merge into: master
  • Upgrade actions/setup-python to e9aba2c848f5ebd159c070c61ea2c4e2b122355e
chore(deps): update dessant/lock-threads action to v2.1.2
  • Schedule: ["every weekday"]
  • Branch name: renovate/dessant-lock-threads-2.x
  • Merge into: master
  • Upgrade dessant/lock-threads to f1a42f0f44eb83361d617a014663e1a76cf282d2
chore(deps): update jupyter-server/jupyter_releaser action to v1.8.6
  • Schedule: ["every weekday"]
  • Branch name: renovate/jupyter-server-jupyter_releaser-1.x
  • Merge into: master
  • Upgrade jupyter-server/jupyter_releaser to 5e95c6a0e833a25a5cb7c77d709c8d8692d69d77
chore(deps): update actions/cache action to v4
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-cache-4.x
  • Merge into: master
  • Upgrade actions/cache to 5a3ec84eff668545956fd18022155c47e93e2684
chore(deps): update actions/checkout action to v4
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: master
  • Upgrade actions/checkout to 11bd71901bbe5b1630ceea73d27597364c9af683
chore(deps): update actions/setup-node action to v4
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-setup-node-4.x
  • Merge into: master
  • Upgrade actions/setup-node to 49933ea5288caeca8642d1e84afbd3f7d6820020
chore(deps): update actions/setup-python action to v5
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-setup-python-5.x
  • Merge into: master
  • Upgrade actions/setup-python to a26af69be951a213d495a4c3e4e4022e16d87065
chore(deps): update dependency @​jupyterlab/apputils to v4
  • Schedule: ["every weekday"]
  • Branch name: renovate/jupyterlab-apputils-4.x
  • Merge into: master
  • Upgrade @jupyterlab/apputils to ^4.0.0
chore(deps): update dependency babel-loader to v10
  • Schedule: ["every weekday"]
  • Branch name: renovate/babel-loader-10.x
  • Merge into: master
  • Upgrade babel-loader to ^10.0.0
chore(deps): update dependency less to v4
  • Schedule: ["every weekday"]
  • Branch name: renovate/less-4.x
  • Merge into: master
  • Upgrade less to ~4.3.0
chore(deps): update dependency node to v22
  • Schedule: ["every weekday"]
  • Branch name: renovate/node-22.x
  • Merge into: master
  • Upgrade node to 22.x
chore(deps): update dependency onchange to v7
  • Schedule: ["every weekday"]
  • Branch name: renovate/onchange-7.x
  • Merge into: master
  • Upgrade onchange to ^7.0.0
chore(deps): update dependency webpack-cli to v6
  • Schedule: ["every weekday"]
  • Branch name: renovate/webpack-cli-6.x
  • Merge into: master
  • Upgrade webpack-cli to ^6.0.0
chore(deps): update dessant/lock-threads action to v5
  • Schedule: ["every weekday"]
  • Branch name: renovate/dessant-lock-threads-5.x
  • Merge into: master
  • Upgrade dessant/lock-threads to 1bf7ec25051fe7c00bdd17e6a7cf3d7bfb7dc771
chore(deps): update r-lib/actions action to v2
  • Schedule: ["every weekday"]
  • Branch name: renovate/r-lib-actions-2.x
  • Merge into: master
  • Upgrade r-lib/actions to bd49c52ffe281809afa6f0fecbf37483c5dd0b93

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR has been generated by Renovate Bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants