Skip to content

Configure Renovate#11

Closed
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/configure
Closed

Configure Renovate#11
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/configure

Conversation

@renovate
Copy link

@renovate renovate bot commented Jun 9, 2020

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/on-push.yml (github-actions)
  • package.json (npm)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • 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 (except for nuget) 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 14 Pull Requests:

Update dependency yaml to v2.2.2 [SECURITY]
  • Branch name: renovate/npm-yaml-vulnerability
  • Merge into: master
  • Upgrade yaml to 2.2.2
Replace dependency npm-run-all with npm-run-all2 ^5.0.0
  • Schedule: ["at any time"]
  • Branch name: renovate/npm-run-all-replacement
  • Merge into: master
  • Upgrade npm-run-all to ^5.0.0
Update dependency husky to v8.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/husky-8.x-lockfile
  • Merge into: master
  • Upgrade husky to 8.0.3
Update dependency @​actions/core to v1.11.1
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-core-1.x-lockfile
  • Merge into: master
  • Upgrade @actions/core to 1.11.1
Update dependency @​vercel/ncc to ^0.38.0
  • Schedule: ["at any time"]
  • Branch name: renovate/vercel-ncc-0.x
  • Merge into: master
  • Upgrade @vercel/ncc to ^0.38.0
Update dependency eslint to v8.57.1
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: master
  • Upgrade eslint to 8.57.1
Update dependency jest to v29.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-monorepo
  • Merge into: master
  • Upgrade jest to 29.7.0
Update dependency nock to v13.5.6
  • Schedule: ["at any time"]
  • Branch name: renovate/nock-13.x-lockfile
  • Merge into: master
  • Upgrade nock to 13.5.6
Update dependency node-fetch to v2.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/node-fetch-2.x-lockfile
  • Merge into: master
  • Upgrade node-fetch to 2.7.0
Update dependency eslint to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: master
  • Upgrade eslint to ^9.0.0
Update dependency husky to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/husky-9.x
  • Merge into: master
  • Upgrade husky to ^9.0.0
Update dependency jest-junit to v16
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-junit-16.x
  • Merge into: master
  • Upgrade jest-junit to ^16.0.0
Update dependency nock to v14
  • Schedule: ["at any time"]
  • Branch name: renovate/nock-14.x
  • Merge into: master
  • Upgrade nock to ^14.0.0
Update dependency node-fetch to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/node-fetch-3.x
  • Merge into: master
  • Upgrade node-fetch to ^3.0.0

🚸 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 was generated by Mend Renovate. View the repository job log.

@atlassian-cla-bot
Copy link

atlassian-cla-bot bot commented Jun 9, 2020

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution.
If your email is listed below, please ensure that you sign the CLA with the same email address.

The following users still need to sign our CLA:
❌renovate[bot]

Already signed the CLA? To re-check, try refreshing the page.

@renovate renovate bot force-pushed the renovate/configure branch from 212b744 to ed7285e Compare October 27, 2020 15:58
@renovate renovate bot force-pushed the renovate/configure branch from ed7285e to e53a496 Compare June 26, 2022 09:22
@renovate renovate bot force-pushed the renovate/configure branch from e53a496 to 7768362 Compare March 23, 2023 23:54
@renovate renovate bot requested a review from a team as a code owner March 23, 2023 23:54
@renovate renovate bot force-pushed the renovate/configure branch from 7768362 to 62ba8f8 Compare December 5, 2023 02:26
@renovate renovate bot force-pushed the renovate/configure branch from 62ba8f8 to 6383270 Compare December 15, 2023 15:00
@renovate renovate bot force-pushed the renovate/configure branch from 6383270 to 0f02351 Compare February 26, 2025 02:53
@renovate renovate bot force-pushed the renovate/configure branch from 0f02351 to 1108b1e Compare March 1, 2025 03:50
@renovate renovate bot closed this Jan 26, 2026
@renovate
Copy link
Author

renovate bot commented Jan 26, 2026

Renovate is disabled

Renovate is disabled because the onboarding PR has been unmerged for more than 366 days. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.

@atlassian
Copy link

atlassian bot commented Jan 26, 2026

To enable Rovo Dev code reviews, link your GitHub account to your Atlassian account.

This is a one-time task that takes less than a minute. Once your account is linked, resubmit the pull request to trigger a code review.

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