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

Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 14, 2020

Mend Renovate

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)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 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 12 Pull Requests:

fix(deps): update dependency redis to v3.1.1 [security]
  • Branch name: renovate/npm-redis-vulnerability
  • Merge into: master
  • Upgrade redis to 3.1.1
chore(deps): update dependency @​types/bcrypt to v3.0.1
  • Schedule: ["at any time"]
  • Branch name: renovate/bcrypt-3.x
  • Merge into: master
  • Upgrade @types/bcrypt to 3.0.1
chore(deps): update dependency @​types/cryptr to v4.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/cryptr-4.x
  • Merge into: master
  • Upgrade @types/cryptr to 4.0.3
chore(deps): update dependency @​types/is-base64 to v1.1.3
  • Schedule: ["at any time"]
  • Branch name: renovate/is-base64-1.x
  • Merge into: master
  • Upgrade @types/is-base64 to 1.1.3
chore(deps): update dependency @​types/pako to v1.0.7
  • Schedule: ["at any time"]
  • Branch name: renovate/pako-1.x
  • Merge into: master
  • Upgrade @types/pako to 1.0.7
chore(deps): update dependency @​types/redis to v2.8.32
  • Schedule: ["at any time"]
  • Branch name: renovate/redis-2.x
  • Merge into: master
  • Upgrade @​types/redis to 2.8.32
fix(deps): update dependency @​vercel/node to v1.15.4
  • Schedule: ["at any time"]
  • Branch name: renovate/vercel-node-1.x
  • Merge into: master
  • Upgrade @vercel/node to 1.15.4
fix(deps): update dependency cryptr to v6.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/cryptr-6.x
  • Merge into: master
  • Upgrade cryptr to 6.3.0
chore(deps): update dependency @​types/redis to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/redis-4.x
  • Merge into: master
  • Upgrade @​types/redis to 4.0.10
fix(deps): update dependency @​vercel/node to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/vercel-node-3.x
  • Merge into: master
  • Upgrade @vercel/node to 3.0.12
fix(deps): update dependency bcrypt to v5.1.1
  • Schedule: ["at any time"]
  • Branch name: renovate/bcrypt-5.x
  • Merge into: master
  • Upgrade bcrypt to 5.1.1
  • Upgrade @types/bcrypt to 5.0.2
fix(deps): update dependency pako to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/pako-2.x
  • Merge into: master
  • Upgrade pako to 2.1.0
  • Upgrade @types/pako to 2.0.3

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.


❓ 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 Mend Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented Jul 16, 2020

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nampdn96/yank-one/8unixglrk
✅ Preview: https://yank-one-git-renovate-configure.nampdn96.vercel.app

@vercel
Copy link

vercel bot commented Jun 26, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
yank-one ❌ Failed (Inspect) Dec 15, 2023 8:27pm

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

Successfully merging this pull request may close these issues.

0 participants