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

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

chore: Configure Renovate #31

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 21, 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/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 19 Pull Requests:

chore(deps): update dependency @​swc/jest to v0.2.36
  • Schedule: ["at any time"]
  • Branch name: renovate/swc-monorepo
  • Merge into: master
  • Upgrade @swc/jest to 0.2.36
chore(deps): update dependency lint-staged to v15.2.2
  • Schedule: ["at any time"]
  • Branch name: renovate/lint-staged-15.x-lockfile
  • Merge into: master
  • Upgrade lint-staged to 15.2.2
chore(deps): update dependency tsup to v8.0.2
  • Schedule: ["at any time"]
  • Branch name: renovate/tsup-8.x-lockfile
  • Merge into: master
  • Upgrade tsup to 8.0.2
fix(deps): update dependency @​manypkg/get-packages to v2.2.1
  • Schedule: ["at any time"]
  • Branch name: renovate/manypkg-get-packages-2.x-lockfile
  • Merge into: master
  • Upgrade @​manypkg/get-packages to 2.2.1
chore(deps): update codecov/codecov-action action to v4.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/codecov-codecov-action-4.x
  • Merge into: master
  • Upgrade codecov/codecov-action to v4.1.0
chore(deps): update dependency @​types/node to v20.11.30
  • Schedule: ["at any time"]
  • Branch name: renovate/node-20.x-lockfile
  • Merge into: master
  • Upgrade @types/node to 20.11.30
chore(deps): update dependency eslint to v8.57.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-8.x-lockfile
  • Merge into: master
  • Upgrade eslint to 8.57.0
chore(deps): update dependency prettier to v3.2.5
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x-lockfile
  • Merge into: master
  • Upgrade prettier to 3.2.5
chore(deps): update dependency typescript to v5.4.3
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x-lockfile
  • Merge into: master
  • Upgrade typescript to 5.4.3
chore(deps): update node.js to v18.19.1
  • Schedule: ["at any time"]
  • Branch name: renovate/node-18.x
  • Merge into: master
  • Upgrade node to 18.19.1
chore(deps): update typescript-eslint monorepo to v6.21.0
fix(deps): update dependency @​changesets/read to ^0.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/changesets-read-0.x
  • Merge into: master
  • Upgrade @changesets/read to ^0.6.0
fix(deps): update dependency @​changesets/write to ^0.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/changesets-write-0.x
  • Merge into: master
  • Upgrade @changesets/write to ^0.3.0
chore(deps): update actions/checkout action 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 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 dependency husky to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/husky-9.x
  • Merge into: master
  • Upgrade husky to ^9.0.0
chore(deps): update node.js to v20
  • Schedule: ["at any time"]
  • Branch name: renovate/node-20.x
  • Merge into: master
  • Upgrade node to 20.11.1
chore(deps): update typescript-eslint monorepo to v7 (major)
fix(deps): update dependency @​changesets/types to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/changesets-types-6.x
  • Merge into: master
  • Upgrade @changesets/types to ^6.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.

Copy link

changeset-bot bot commented Mar 21, 2024

⚠️ No Changeset found

Latest commit: 1bfe54c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link

codecov bot commented Mar 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 42.42%. Comparing base (50bf163) to head (1bfe54c).

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #31   +/-   ##
=======================================
  Coverage   42.42%   42.42%           
=======================================
  Files           2        2           
  Lines          66       66           
  Branches       10       10           
=======================================
  Hits           28       28           
  Misses         38       38           

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

0 participants