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

Merged
merged 1 commit into from
Nov 17, 2022
Merged

Configure Renovate #163

merged 1 commit into from
Nov 17, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 17, 2022

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

  • apps/backend/docker-compose.yml (docker-compose)
  • Dockerfile.backend (dockerfile)
  • Dockerfile.frontend (dockerfile)
  • .github/workflows/cd.yml (github-actions)
  • .github/workflows/e2e-test.yml (github-actions)
  • .github/workflows/unit-test.yml (github-actions)
  • apps/backend/package.json (npm)
  • apps/frontend/package.json (npm)
  • package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Enable Renovate Dependency Dashboard creation.
  • If Renovate detects semantic commits, it will use semantic commit type fix for dependencies and chore for all others.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Autodetect whether to pin dependencies or maintain ranges.
  • Rate limit PR creation to a maximum of two per hour.
  • Limit to maximum 10 open PRs at any time.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • A collection of workarounds for known problems with packages.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


What to Expect

With your current configuration, Renovate will create 18 Pull Requests:

chore(deps): update dependency @​nuxt/test-utils to v3.0.0
  • Schedule: ["at any time"]
  • Branch name: renovate/nuxt-test-utils-3.x
  • Merge into: master
  • Upgrade @nuxt/test-utils to 3.0.0
chore(deps): update dependency @​types/connect-redis to ^0.0.19
  • Schedule: ["at any time"]
  • Branch name: renovate/connect-redis-0.x
  • Merge into: master
  • Upgrade @types/connect-redis to ^0.0.19
chore(deps): update dependency nuxt to v3.0.0
  • Schedule: ["at any time"]
  • Branch name: renovate/nuxt-3.x
  • Merge into: master
  • Upgrade nuxt to 3.0.0
chore(deps): update dependency @​types/jest to v27.5.2
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-monorepo
  • Merge into: master
  • Upgrade @types/jest to 27.5.2
chore(deps): update dependency vitest to ^0.25.0
  • Schedule: ["at any time"]
  • Branch name: renovate/vitest-monorepo
  • Merge into: master
  • Upgrade vitest to ^0.25.0
fix(deps): update dependency isomorphic-dompurify to ^0.24.0
  • Schedule: ["at any time"]
  • Branch name: renovate/isomorphic-dompurify-0.x
  • Merge into: master
  • Upgrade isomorphic-dompurify to ^0.24.0
chore(deps): update actions/checkout action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-3.x
  • Merge into: master
  • Upgrade actions/checkout to v3
chore(deps): update dependency @​nuxtjs/tailwindcss to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/nuxtjs-tailwindcss-6.x
  • Merge into: master
  • Upgrade @nuxtjs/tailwindcss to ^6.0.0
chore(deps): update dependency @​types/node to v18
  • Schedule: ["at any time"]
  • Branch name: renovate/node-18.x
  • Merge into: master
  • Upgrade @types/node to ^18.0.0
chore(deps): update dependency cypress to v11
  • Schedule: ["at any time"]
  • Branch name: renovate/cypress-11.x
  • Merge into: master
  • Upgrade cypress to ^11.0.0
chore(deps): update dependency tsconfig-paths to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/tsconfig-paths-4.x
  • Merge into: master
  • Upgrade tsconfig-paths to ^4.0.0
chore(deps): update jest monorepo to v29 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jest-monorepo
  • Merge into: master
  • Upgrade @types/jest to 29.2.3
  • Upgrade jest to ^29.0.0
  • Upgrade ts-jest to ^29.0.0
chore(deps): update node.js to v19
  • Schedule: ["at any time"]
  • Branch name: renovate/node-19.x
  • Merge into: master
  • Upgrade node to 19.1-bullseye
fix(deps): update dependency @​casl/ability to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/casl-ability-6.x
  • Merge into: master
  • Upgrade @casl/ability to ^6.0.0
fix(deps): update dependency @​nestjs/axios to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/nestjs-axios-1.x
  • Merge into: master
  • Upgrade @nestjs/axios to ^1.0.0
fix(deps): update dependency file-type to v18
  • Schedule: ["at any time"]
  • Branch name: renovate/file-type-18.x
  • Merge into: master
  • Upgrade file-type to ^18.0.0
fix(deps): update dependency helmet to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/helmet-6.x
  • Merge into: master
  • Upgrade helmet to ^6.0.0
fix(deps): update dependency redis to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/redis-4.x
  • Merge into: master
  • Upgrade redis to ^4.0.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam 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.

@ppodds ppodds merged commit ff4a2ce into master Nov 17, 2022
@renovate renovate bot deleted the renovate/configure branch November 17, 2022 11:20
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.

None yet

1 participant