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

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

Configure Renovate #2

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 10, 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

  • .circleci/config.yml (circleci)
  • .github/workflows/analysis.yml (github-actions)
  • .github/workflows/chromatic.yml (github-actions)
  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/coverage.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 58 Pull Requests:

chore(deps): update dependency eslint-plugin-storybook to v0.6.15
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-storybook-0.x-lockfile
  • Merge into: main
  • Upgrade eslint-plugin-storybook to 0.6.15
chore(deps): update dependency plop to v3.1.2
  • Schedule: ["at any time"]
  • Branch name: renovate/plop-3.x-lockfile
  • Merge into: main
  • Upgrade plop to 3.1.2
chore(deps): update dependency postcss-scss to v4.0.9
  • Schedule: ["at any time"]
  • Branch name: renovate/postcss-scss-4.x-lockfile
  • Merge into: main
  • Upgrade postcss-scss to 4.0.9
chore(deps): update dependency prettier to v2.8.8
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-2.x-lockfile
  • Merge into: main
  • Upgrade prettier to 2.8.8
chore(deps): update dependency ts-node to v10.9.2
  • Schedule: ["at any time"]
  • Branch name: renovate/ts-node-10.x-lockfile
  • Merge into: main
  • Upgrade ts-node to 10.9.2
chore(deps): update peter-evans/create-or-update-comment action to v1.4.5
chore(deps): update semantic-release monorepo
fix(deps): update dependency keen-slider to v6.8.6
  • Schedule: ["at any time"]
  • Branch name: renovate/keen-slider-6.x-lockfile
  • Merge into: main
  • Upgrade keen-slider to 6.8.6
chore(deps): update actions/checkout action to v3.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-3.x
  • Merge into: main
  • Upgrade actions/checkout to v3.6.0
chore(deps): update cimg/python docker tag to v3.12.1
  • Schedule: ["at any time"]
  • Branch name: renovate/cimg-python-3.x
  • Merge into: main
  • Upgrade cimg/python to 3.12.1
chore(deps): update codecov orb to v3.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/codecov-3.x
  • Merge into: main
  • Upgrade codecov to 3.3.0
chore(deps): update commitlint monorepo to v17.8.1
chore(deps): update dependency @testing-library/jest-dom to v5.17.0
  • Schedule: ["at any time"]
  • Branch name: renovate/testing-library-jest-dom-5.x-lockfile
  • Merge into: main
  • Upgrade @testing-library/jest-dom to 5.17.0
chore(deps): update dependency @​types/node to v18.19.3
  • Schedule: ["at any time"]
  • Branch name: renovate/node-18.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 18.19.3
chore(deps): update dependency @​types/react to v18.2.45
  • Schedule: ["at any time"]
  • Branch name: renovate/react-monorepo
  • Merge into: main
  • Upgrade @types/react to 18.2.45
chore(deps): update dependency chromatic to v6.24.1
  • Schedule: ["at any time"]
  • Branch name: renovate/chromatic-6.x-lockfile
  • Merge into: main
  • Upgrade chromatic to 6.24.1
chore(deps): update dependency eslint to v8.55.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-8.x-lockfile
  • Merge into: main
  • Upgrade eslint to 8.55.0
chore(deps): update dependency eslint-config-prettier to v8.10.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-config-prettier-8.x-lockfile
  • Merge into: main
  • Upgrade eslint-config-prettier to 8.10.0
chore(deps): update dependency eslint-import-resolver-typescript to v3.6.1
chore(deps): update dependency eslint-plugin-import to v2.29.1
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-import-2.x-lockfile
  • Merge into: main
  • Upgrade eslint-plugin-import to 2.29.1
chore(deps): update dependency eslint-plugin-jest to v27.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-jest-27.x-lockfile
  • Merge into: main
  • Upgrade eslint-plugin-jest to 27.6.0
chore(deps): update dependency eslint-plugin-jsx-a11y to v6.8.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-jsx-a11y-6.x-lockfile
  • Merge into: main
  • Upgrade eslint-plugin-jsx-a11y to 6.8.0
chore(deps): update dependency eslint-plugin-react to v7.33.2
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-react-7.x-lockfile
  • Merge into: main
  • Upgrade eslint-plugin-react to 7.33.2
chore(deps): update dependency lint-staged to v13.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lint-staged-13.x-lockfile
  • Merge into: main
  • Upgrade lint-staged to 13.3.0
chore(deps): update dependency storybook-addon-pseudo-states to v2.1.2
  • Schedule: ["at any time"]
  • Branch name: renovate/storybook-addon-pseudo-states-2.x-lockfile
  • Merge into: main
  • Upgrade storybook-addon-pseudo-states to 2.1.2
chore(deps): update dependency storybook-dark-mode to v2.1.1
  • Schedule: ["at any time"]
  • Branch name: renovate/storybook-dark-mode-2.x-lockfile
  • Merge into: main
  • Upgrade storybook-dark-mode to 2.1.1
chore(deps): update jest monorepo
chore(deps): update storybook monorepo to v7.6.4
chore(deps): update typescript-eslint monorepo to v5.62.0
fix(deps): update dependency axios to v1.6.2
  • Schedule: ["at any time"]
  • Branch name: renovate/axios-1.x-lockfile
  • Merge into: main
  • Upgrade axios to 1.6.2
fix(deps): update dependency sharp to ^0.33.0
  • Schedule: ["at any time"]
  • Branch name: renovate/sharp-0.x
  • Merge into: main
  • Upgrade sharp to ^0.33.0
fix(deps): update dependency stripe to v11.18.0
  • Schedule: ["at any time"]
  • Branch name: renovate/stripe-11.x-lockfile
  • Merge into: main
  • Upgrade stripe to 11.18.0
fix(deps): update nextjs monorepo to v13.5.6
chore(deps): update actions/cache action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-cache-3.x
  • Merge into: main
  • Upgrade actions/cache to v3
chore(deps): update actions/checkout action to v4
chore(deps): update actions/setup-node action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-4.x
  • Merge into: main
  • Upgrade actions/setup-node to v4
chore(deps): update actions/upload-artifact action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-upload-artifact-4.x
  • Merge into: main
  • Upgrade actions/upload-artifact to v4
chore(deps): update chromaui/action action to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/chromaui-action-10.x
  • Merge into: main
  • Upgrade chromaui/action to v10
chore(deps): update commitlint monorepo to v18 (major)
chore(deps): update dawidd6/action-download-artifact action to v3
chore(deps): update dependency @testing-library/jest-dom to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/testing-library-jest-dom-6.x
  • Merge into: main
  • Upgrade @testing-library/jest-dom to ^6.0.0
chore(deps): update dependency @testing-library/react to v14
  • Schedule: ["at any time"]
  • Branch name: renovate/testing-library-react-14.x
  • Merge into: main
  • Upgrade @testing-library/react to ^14.0.0
chore(deps): update dependency @​types/node to v20
  • Schedule: ["at any time"]
  • Branch name: renovate/node-20.x
  • Merge into: main
  • Upgrade @types/node to ^20.0.0
chore(deps): update dependency chromatic to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/chromatic-10.x
  • Merge into: main
  • Upgrade chromatic to ^10.0.0
chore(deps): update dependency eslint-config-prettier to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-config-prettier-9.x
  • Merge into: main
  • Upgrade eslint-config-prettier to ^9.0.0
chore(deps): update dependency eslint-plugin-prettier to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-prettier-5.x
  • Merge into: main
  • Upgrade eslint-plugin-prettier to ^5.0.0
chore(deps): 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
chore(deps): update dependency plop to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/plop-4.x
  • Merge into: main
  • Upgrade plop to ^4.0.0
chore(deps): update dependency prettier to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x
  • Merge into: main
  • Upgrade prettier to ^3.0.0
chore(deps): 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
chore(deps): update dependency storybook-dark-mode to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/storybook-dark-mode-3.x
  • Merge into: main
  • Upgrade storybook-dark-mode to ^3.0.0
chore(deps): update dependency typescript to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x
  • Merge into: main
  • Upgrade typescript to ^5.0.0
chore(deps): update peter-evans/create-or-update-comment action to v3
chore(deps): update peter-evans/find-comment action to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/peter-evans-find-comment-2.x
  • Merge into: main
  • Upgrade peter-evans/find-comment to v2
chore(deps): update typescript-eslint monorepo to v6 (major)
fix(deps): update dependency next-seo to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/next-seo-6.x
  • Merge into: main
  • Upgrade next-seo to ^6.0.0
fix(deps): update dependency stripe to v14
  • Schedule: ["at any time"]
  • Branch name: renovate/stripe-14.x
  • Merge into: main
  • Upgrade stripe to ^14.0.0
fix(deps): update nextjs monorepo to v14 (major)

🚸 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 Jun 10, 2023

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

Name Status Preview Comments Updated (UTC)
ignite-shop ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 15, 2023 11:39am

@codecov
Copy link

codecov bot commented Jun 10, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

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

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage        ?   87.93%           
=======================================
  Files           ?       12           
  Lines           ?       58           
  Branches        ?        0           
=======================================
  Hits            ?       51           
  Misses          ?        7           
  Partials        ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

This PR has 4 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +4 -0
Percentile : 1.6%

Total files changed: 1

Change summary by file extension:
.json : +4 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

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

Successfully merging this pull request may close these issues.

0 participants