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

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

Configure Renovate #7

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 1, 2023

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/issue-auto-comments.yml (github-actions)
  • .github/workflows/issue-check-inactive.yml (github-actions)
  • .github/workflows/issue-close-require.yml (github-actions)
  • .github/workflows/release.yml (github-actions)
  • .github/workflows/test.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 9 Pull Requests:

Update dependency father to v4.3.8
  • Schedule: ["at any time"]
  • Branch name: renovate/father-4.x
  • Merge into: main
  • Upgrade father to 4.3.8
Update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to v4
Update commitlint monorepo to v18 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-commitlint-monorepo
  • Merge into: main
  • Upgrade @commitlint/cli to ^18.0.0
  • Upgrade commitlint to ^18.0.0
Update dependency @​vercel/node to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/vercel-node-3.x
  • Merge into: main
  • Upgrade @vercel/node to ^3.0.0
Update dependency lint-staged to v15
  • Schedule: ["at any time"]
  • Branch name: renovate/lint-staged-15.x
  • Merge into: main
  • Upgrade lint-staged to ^15.0.0
Update dependency semantic-release to v22
  • Schedule: ["at any time"]
  • Branch name: renovate/major-semantic-release-monorepo
  • Merge into: main
  • Upgrade semantic-release to ^22.0.0
Update dependency vercel to v33
  • Schedule: ["at any time"]
  • Branch name: renovate/vercel-33.x
  • Merge into: main
  • Upgrade vercel to ^33.0.0
Update remark (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-remark
  • Merge into: main
  • Upgrade remark to ^15.0.0
  • Upgrade remark-cli to ^12.0.0
Update vitest monorepo to v1 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-vitest-monorepo
  • Merge into: main
  • Upgrade @vitest/coverage-v8 to 1.1.0
  • Upgrade vitest to 1.1.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.

@Isratja45
Copy link

M

@Isratja45
Copy link

K

Copy link

codecov bot commented Dec 15, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (main@5306fb6). Click here to learn what that means.

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #7   +/-   ##
=======================================
  Coverage        ?   80.71%           
=======================================
  Files           ?        4           
  Lines           ?      612           
  Branches        ?       78           
=======================================
  Hits            ?      494           
  Misses          ?      118           
  Partials        ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it 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.

1 participant