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 #107

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

Configure Renovate #107

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 4, 2024

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

  • .github/workflows/nodejs.yml (github-actions)
  • .github/workflows/npmpublish.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
  • 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.
  • Enable Renovate Dependency Dashboard creation.
  • Pin all dependency versions except peerDependencies.
  • Special rules covering major version updates.
  • Rules governing github actions.
  • Base Renovate configuration for Expedia Group projects

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

fix(deps): pin dependencies
fix(deps): pin dependencies
chore(deps): update devdependencies tape from v4.15.1 to ^4.17.0
  • Schedule: ["at any time"]
  • Branch name: renovate/tape-4.x
  • Merge into: master
  • Upgrade tape to ^4.17.0
feat(deps): update dependencies @graphql-tools/utils from v8.9.0 to ^8.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/graphql-tools-monorepo
  • Merge into: master
  • Upgrade @graphql-tools/utils to ^8.9.0
chore(deps): update actions/checkout action from vv2 to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: master
  • Upgrade actions/checkout to v4
chore(deps): update actions/setup-node action from vv1 to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-4.x
  • Merge into: master
  • Upgrade actions/setup-node to v4
chore(deps): update devdependencies eslint from v6.8.0 to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-8.x
  • Merge into: master
  • Upgrade eslint to ^8.0.0
chore(deps): update devdependencies nyc from v14.1.1 to v15
  • Schedule: ["at any time"]
  • Branch name: renovate/nyc-15.x
  • Merge into: master
  • Upgrade nyc to ^15.0.0
chore(deps): update devdependencies sinon from v12.0.1 to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/sinon-17.x
  • Merge into: master
  • Upgrade sinon to ^17.0.0
chore(deps): update devdependencies tape from v4.15.1 to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/tape-5.x
  • Merge into: master
  • Upgrade tape to ^5.0.0
feat(deps): update graphql-tools monorepo (major)

❓ 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.

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