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

chore: Configure Renovate #69

Closed
wants to merge 1 commit into from
Closed

chore: Configure Renovate #69

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 8, 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/on-release-creation-publish-to-npm.yml (github-actions)
  • .github/workflows/prerelease.yml (github-actions)
  • .github/workflows/run-tests-on-pr-and-push-to-main.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.

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

chore(deps): replace dependency eslint-plugin-node with eslint-plugin-n ^14.0.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-node-replacement
  • Merge into: main
  • Upgrade eslint-plugin-node to ^14.0.0
chore(deps): update dependency @​adobe/eslint-config-aio-lib-config to v4
chore(deps): update dependency acorn to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/acorn-8.x
  • Merge into: main
  • Upgrade acorn to ^8.0.0
chore(deps): update dependency eslint to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-9.x
  • Merge into: main
  • Upgrade eslint to ^9.0.0
chore(deps): update dependency eslint-config-oclif to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-config-oclif-5.x
  • Merge into: main
  • Upgrade eslint-config-oclif to ^5.0.0
chore(deps): update dependency eslint-plugin-jest to v28
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-jest-28.x
  • Merge into: main
  • Upgrade eslint-plugin-jest to ^28.0.0
chore(deps): update dependency eslint-plugin-jsdoc to v48
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-jsdoc-48.x
  • Merge into: main
  • Upgrade eslint-plugin-jsdoc to ^48.0.0
chore(deps): update dependency eslint-plugin-n to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-n-17.x
  • Merge into: main
  • Upgrade eslint-plugin-n to ^17.0.0
chore(deps): update dependency eslint-plugin-standard to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-standard-5.x
  • Merge into: main
  • Upgrade eslint-plugin-standard to ^5.0.0
chore(deps): update dependency jest-junit to v16
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-junit-16.x
  • Merge into: main
  • Upgrade jest-junit to ^16.0.0
chore(deps): update jest monorepo to v29 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jest-monorepo
  • Merge into: main
  • Upgrade @types/jest to ^29.0.0
  • Upgrade jest-resolve to ^29.0.0
fix(deps): update dependency @​oclif/core to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/oclif-core-3.x
  • Merge into: main
  • Upgrade @oclif/core to ^3.0.0
fix(deps): update dependency chalk to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/chalk-5.x
  • Merge into: main
  • Upgrade chalk to ^5.0.0
fix(deps): update dependency execa to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/execa-8.x
  • Merge into: main
  • Upgrade execa to ^8.0.0
fix(deps): update dependency fs-extra to v11
  • Schedule: ["at any time"]
  • Branch name: renovate/fs-extra-11.x
  • Merge into: main
  • Upgrade fs-extra to ^11.0.0
fix(deps): update dependency inquirer to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/inquirer-9.x
  • Merge into: main
  • Upgrade inquirer to ^9.0.0
fix(deps): update dependency js-yaml to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/js-yaml-4.x
  • Merge into: main
  • Upgrade js-yaml to ^4.0.0
fix(deps): update dependency node-fetch to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/node-fetch-3.x
  • Merge into: main
  • Upgrade node-fetch to ^3.0.0
fix(deps): update dependency ora to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/ora-8.x
  • Merge into: main
  • Upgrade ora to ^8.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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/configure branch from 7920769 to aeb6d08 Compare April 10, 2024 01:33
@shazron shazron closed this May 14, 2024
Copy link
Author

renovate bot commented May 14, 2024

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. 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.

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.

1 participant