Skip to content
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

Configure Renovate #1

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

  • package.json (npm)
  • seans_example/package.json (npm)

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.
  • Pin github-action digests.
  • 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 16 Pull Requests:

chore(deps): update dependency hem to ~0.3.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/hem-0.x
  • Merge into: master
  • Upgrade hem to ~0.3.0
chore(deps): update dependency hem-less to ~0.1.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/hem-less-0.x
  • Merge into: master
  • Upgrade hem-less to ~0.1.0
chore(deps): update dependency http-proxy to ~0.10.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/http-proxy-0.x
  • Merge into: master
  • Upgrade http-proxy to ~0.10.0
chore(deps): update dependency less to ~1.7.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/less-1.x
  • Merge into: master
  • Upgrade less to ~1.7.0
chore(deps): update dependency optimist to ~0.6.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/optimist-0.x
  • Merge into: master
  • Upgrade optimist to ~0.6.0
chore(deps): update dependency testacular to ~0.6.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/testacular-0.x
  • Merge into: master
  • Upgrade testacular to ~0.6.0
chore(deps): update dependency underscore to ~1.13.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/underscore-1.x
  • Merge into: master
  • Upgrade underscore to ~1.13.0
chore(deps): update dependency watch to ~0.19.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/watch-0.x
  • Merge into: master
  • Upgrade watch to ~0.19.0
chore(deps): update dependency backbone to v1
  • Schedule: ["every weekday"]
  • Branch name: renovate/backbone-1.x
  • Merge into: master
  • Upgrade backbone to ~1.6.0
chore(deps): update dependency es5-shimify to v2
  • Schedule: ["every weekday"]
  • Branch name: renovate/es5-shimify-2.x
  • Merge into: master
  • Upgrade es5-shimify to ~2.3.0
chore(deps): update dependency hem to v1
  • Schedule: ["every weekday"]
  • Branch name: renovate/hem-1.x
  • Merge into: master
  • Upgrade hem to ~1.0.0
chore(deps): update dependency http-proxy to v1
  • Schedule: ["every weekday"]
  • Branch name: renovate/http-proxy-1.x
  • Merge into: master
  • Upgrade http-proxy to ~1.18.0
chore(deps): update dependency jqueryify to v1
  • Schedule: ["every weekday"]
  • Branch name: renovate/jqueryify-1.x
  • Merge into: master
  • Upgrade jqueryify to ~1.11.0
chore(deps): update dependency less to v4
  • Schedule: ["every weekday"]
  • Branch name: renovate/less-4.x
  • Merge into: master
  • Upgrade less to ~4.2.0
chore(deps): update dependency uglify-js to v3
  • Schedule: ["every weekday"]
  • Branch name: renovate/uglify-js-3.x
  • Merge into: master
  • Upgrade uglify-js to ~3.19.0
chore(deps): update dependency watch to v1
  • Schedule: ["every weekday"]
  • Branch name: renovate/watch-1.x
  • Merge into: master
  • Upgrade watch to ~1.0.0

❓ 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