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 - autoclosed #38

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 20, 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

  • docker-compose.debug.yml (docker-compose)
  • docker-compose.yml (docker-compose)
  • .devcontainer/Dockerfile (dockerfile)
  • Dockerfile (dockerfile)
  • .github/actions/codeql-analysis/action.yml (github-actions)
  • .github/actions/publish-docker/action.yml (github-actions)
  • .github/workflows/create-pre-release.yml (github-actions)
  • .github/workflows/create-release.yml (github-actions)
  • .github/workflows/deploy-k8s.yml (github-actions)
  • .github/workflows/node-ci.yml (github-actions)
  • .github/workflows/rc-release.yml (github-actions)
  • package.json (npm)
  • .nvmrc (nvm)

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

chore(deps): 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
chore(deps): update dependency @​eslint/eslintrc to v2.1.4
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-eslintrc-2.x-lockfile
  • Merge into: master
  • Upgrade @eslint/eslintrc to 2.1.4
chore(deps): update dependency @​travi/any to v2.1.10
  • Schedule: ["at any time"]
  • Branch name: renovate/travi-any-2.x-lockfile
  • Merge into: master
  • Upgrade @travi/any to 2.1.10
chore(deps): update dependency smee-client to v1.2.5
  • Schedule: ["at any time"]
  • Branch name: renovate/smee-client-1.x-lockfile
  • Merge into: master
  • Upgrade smee-client to 1.2.5
fix(deps): update dependency @​probot/adapter-aws-lambda-serverless to v3.0.4
fix(deps): update dependency node-cron to v3.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/node-cron-3.x-lockfile
  • Merge into: master
  • Upgrade node-cron to 3.0.3
chore(deps): update dependency check-engine to v1.12.0
  • Schedule: ["at any time"]
  • Branch name: renovate/check-engine-1.x-lockfile
  • Merge into: master
  • Upgrade check-engine to 1.12.0
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 eslint-config-standard to v17.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-config-standard-17.x-lockfile
  • Merge into: master
  • Upgrade eslint-config-standard to 17.1.0
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: master
  • Upgrade eslint-plugin-import to 2.29.1
chore(deps): update dependency eslint-plugin-promise to v6.1.1
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-promise-6.x-lockfile
  • Merge into: master
  • Upgrade eslint-plugin-promise to 6.1.1
chore(deps): update dependency http-status-codes to v2.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/http-status-codes-2.x-lockfile
  • Merge into: master
  • Upgrade http-status-codes to 2.3.0
chore(deps): update dependency jest to v29.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-monorepo
  • Merge into: master
  • Upgrade jest to 29.7.0
chore(deps): update dependency jest-when to v3.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-when-3.x-lockfile
  • Merge into: master
  • Upgrade jest-when to 3.6.0
chore(deps): update dependency lockfile-lint to v4.13.2
  • Schedule: ["at any time"]
  • Branch name: renovate/lockfile-lint-4.x-lockfile
  • Merge into: master
  • Upgrade lockfile-lint to 4.13.2
chore(deps): update dependency nock to v13.5.4
  • Schedule: ["at any time"]
  • Branch name: renovate/nock-13.x-lockfile
  • Merge into: master
  • Upgrade nock to 13.5.4
chore(deps): update dependency standard to v17.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/standard-17.x-lockfile
  • Merge into: master
  • Upgrade standard to 17.1.0
fix(deps): update dependency @​opentelemetry/api to v1.8.0
  • Schedule: ["at any time"]
  • Branch name: renovate/opentelemetry-js-monorepo
  • Merge into: master
  • Upgrade @opentelemetry/api to 1.8.0
fix(deps): update dependency @​opentelemetry/auto-instrumentations-node to ^0.43.0
fix(deps): update dependency @​opentelemetry/instrumentation-pino to ^0.36.0
fix(deps): update dependency eta to v3.4.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eta-3.x-lockfile
  • Merge into: master
  • Upgrade eta to 3.4.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 azure/aks-set-context action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/azure-aks-set-context-4.x
  • Merge into: master
  • Upgrade azure/aks-set-context to v4
chore(deps): update azure/login action to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/azure-login-2.x
  • Merge into: master
  • Upgrade azure/login to v2
chore(deps): update dependency @​eslint/eslintrc to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-eslintrc-3.x
  • Merge into: master
  • Upgrade @eslint/eslintrc to ^3.0.0
chore(deps): update dependency @​travi/any to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/travi-any-3.x
  • Merge into: master
  • Upgrade @travi/any to ^3.0.0
chore(deps): update dependency node to v20
  • Schedule: ["at any time"]
  • Branch name: renovate/node-20.x
  • Merge into: master
  • Upgrade node to 20
  • Upgrade node to 20-alpine
chore(deps): update dependency nodemon to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/nodemon-3.x
  • Merge into: master
  • Upgrade nodemon to ^3.0.0
chore(deps): update dependency smee-client to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/smee-client-2.x
  • Merge into: master
  • Upgrade smee-client to ^2.0.0
chore(deps): update docker/build-push-action action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-build-push-action-5.x
  • Merge into: master
  • Upgrade docker/build-push-action to v5
chore(deps): update docker/login-action action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-3.x
  • Merge into: master
  • Upgrade docker/login-action to v3
chore(deps): update docker/metadata-action action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-metadata-action-5.x
  • Merge into: master
  • Upgrade docker/metadata-action to v5
chore(deps): update docker/setup-buildx-action action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-setup-buildx-action-3.x
  • Merge into: master
  • Upgrade docker/setup-buildx-action to v3
chore(deps): update docker/setup-qemu-action action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-setup-qemu-action-3.x
  • Merge into: master
  • Upgrade docker/setup-qemu-action to v3
chore(deps): update github/codeql-action action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/github-codeql-action-3.x
  • Merge into: master
  • Upgrade github/codeql-action to v3
chore(deps): update mcr.microsoft.com/vscode/devcontainers/javascript-node docker tag to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/mcr.microsoft.com-vscode-devcontainers-javascript-node-1.x
  • Merge into: master
  • Upgrade mcr.microsoft.com/vscode/devcontainers/javascript-node to 1-16-bullseye
fix(deps): update dependency probot to v13
  • Schedule: ["at any time"]
  • Branch name: renovate/probot-13.x
  • Merge into: master
  • Upgrade probot to ^13.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.

@renovate renovate bot requested a review from a team as a code owner March 20, 2024 09:32
@renovate renovate bot requested a review from stevoland March 20, 2024 09:32
@renovate renovate bot changed the title chore: Configure Renovate chore: Configure Renovate - autoclosed Mar 26, 2024
@renovate renovate bot closed this Mar 26, 2024
@renovate renovate bot deleted the renovate/configure branch March 26, 2024 16:47
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