Configure Renovate

[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/push.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
• Hopefully safe environment variables to allow users to configure.
• 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 (except for nuget) 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 11 Pull Requests:

Update dependency yaml to v2.2.2 [SECURITY]

• Branch name: renovate/npm-yaml-vulnerability
• Merge into: master
• Upgrade yaml to 2.2.2

Replace dependency npm-run-all with npm-run-all2 ^5.0.0

• Schedule: ["at any time"]
• Branch name: renovate/npm-run-all-replacement
• Merge into: master
• Upgrade npm-run-all to ^5.0.0

Update dependency husky to v8.0.3

• Schedule: ["at any time"]
• Branch name: renovate/husky-8.x-lockfile
• Merge into: master
• Upgrade husky to 8.0.3

Update dependency @​vercel/ncc to ^0.38.0

• Schedule: ["at any time"]
• Branch name: renovate/vercel-ncc-0.x
• Merge into: master
• Upgrade @vercel/ncc to ^0.38.0

Update dependency eslint to v8.57.1

• Schedule: ["at any time"]
• Branch name: renovate/eslint-monorepo
• Merge into: master
• Upgrade eslint to 8.57.1

Update dependency moment to v2.30.1

• Schedule: ["at any time"]
• Branch name: renovate/moment-2.x-lockfile
• Merge into: master
• Upgrade moment to 2.30.1

Update dependency node-fetch to v2.7.0

• Schedule: ["at any time"]
• Branch name: renovate/node-fetch-2.x-lockfile
• Merge into: master
• Upgrade node-fetch to 2.7.0

Update dependency yargs to v17.7.2

• Schedule: ["at any time"]
• Branch name: renovate/yargs-17.x-lockfile
• Merge into: master
• Upgrade yargs to 17.7.2

Update dependency eslint to v9

• Schedule: ["at any time"]
• Branch name: renovate/major-eslint-monorepo
• Merge into: master
• Upgrade eslint to ^9.0.0

Update dependency husky to v9

• Schedule: ["at any time"]
• Branch name: renovate/husky-9.x
• Merge into: master
• Upgrade husky to ^9.0.0

Update dependency node-fetch to v3

• Schedule: ["at any time"]
• Branch name: renovate/node-fetch-3.x
• Merge into: master
• Upgrade node-fetch to ^3.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 was generated by Mend Renovate. View the repository job log.

[atlassian-cla-bot]

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution.
If your email is listed below, please ensure that you sign the CLA with the same email address.

The following users still need to sign our CLA:
❌renovate[bot]

_{Already signed the CLA? To re-check, try refreshing the page.}

[ervin210]

F

[ervin210]

See if you stolen and don’t stop try kill me this happens