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

• package.json (npm)
• .travis.yml (travis)

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 15 Pull Requests:

Update dependency moment-timezone to v0.5.35 [SECURITY]

• Branch name: renovate/npm-moment-timezone-vulnerability
• Merge into: develop
• Upgrade moment-timezone to 0.5.35

Update dependency eslint-plugin-react to v6.10.3

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-react-6.x-lockfile
• Merge into: develop
• Upgrade eslint-plugin-react to 6.10.3

Update dependency eslint to v3.19.0

• Schedule: ["at any time"]
• Branch name: renovate/eslint-3.x-lockfile
• Merge into: develop
• Upgrade eslint to 3.19.0

Update dependency eslint-plugin-import to v2.29.1

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-import-2.x-lockfile
• Merge into: develop
• Upgrade eslint-plugin-import to 2.29.1

Update dependency mocha to v3.5.3

• Schedule: ["at any time"]
• Branch name: renovate/mocha-3.x-lockfile
• Merge into: develop
• Upgrade mocha to 3.5.3

Update dependency nyc to v10.3.2

• Schedule: ["at any time"]
• Branch name: renovate/nyc-10.x-lockfile
• Merge into: develop
• Upgrade nyc to 10.3.2

Update dependency sinon to v2.4.1

• Schedule: ["at any time"]
• Branch name: renovate/sinon-2.x-lockfile
• Merge into: develop
• Upgrade sinon to 2.4.1

Update dependency chai to v4

• Schedule: ["at any time"]
• Branch name: renovate/chai-4.x
• Merge into: develop
• Upgrade chai to ^4.0.0

Update dependency eslint to v8

• Schedule: ["at any time"]
• Branch name: renovate/eslint-8.x
• Merge into: develop
• Upgrade eslint to ^8.0.0

Update dependency eslint-config-airbnb to v19

• Schedule: ["at any time"]
• Branch name: renovate/eslint-config-airbnb-19.x
• Merge into: develop
• Upgrade eslint-config-airbnb to ^19.0.0

Update dependency eslint-plugin-jsx-a11y to v6

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-jsx-a11y-6.x
• Merge into: develop
• Upgrade eslint-plugin-jsx-a11y to ^6.0.0

Update dependency eslint-plugin-react to v7

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-react-7.x
• Merge into: develop
• Upgrade eslint-plugin-react to ^7.0.0

Update dependency mocha to v10

• Schedule: ["at any time"]
• Branch name: renovate/mocha-10.x
• Merge into: develop
• Upgrade mocha to ^10.0.0

Update dependency nyc to v15

• Schedule: ["at any time"]
• Branch name: renovate/nyc-15.x
• Merge into: develop
• Upgrade nyc to ^15.0.0

Update dependency sinon to v17

• Schedule: ["at any time"]
• Branch name: renovate/sinon-17.x
• Merge into: develop
• Upgrade sinon to ^17.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.

[ordermentum]

Please make sure to add screenshots or gifs of the change to give a clear
picture of the change. If a design PR was made please make sure to link to it along with the
JIRA ticket. A Design PR will avoid unnecessary rework that might come up in a PR.

Good Pull Requests adhere to a single responsibility.

• Break big changes into smaller Pull Requests
• Big changes increase risk - smaller PRs are easier to review
• Refactoring changes should be in seperate PRs to avoid noise
• A story/ticket can have more than 1 PR

Some guidelines on giving and receiving feedback in Code Reviews

• https://blog.rangle.io/the-art-of-humanizing-pull-requests-prs/
• https://blog.scottnonnenberg.com/top-ten-pull-request-review-mistakes/
• https://dev.to/codemouse92/10-principles-of-a-good-code-review-2egA
• https://dev.to/samjarman/giving-and-receiving-great-code-reviews