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

Merged
merged 1 commit into from
Sep 16, 2023
Merged

Configure Renovate #115

merged 1 commit into from
Sep 16, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 16, 2023

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

  • docs/Gemfile (bundler)
  • docker-compose/ELK/docker-compose.yml (docker-compose)
  • docker-compose/SEQ/docker-compose.yml (docker-compose)
  • docs/docker-compose.yml (docker-compose)
  • Dockerfile (dockerfile)
  • docker-compose/Dockerfile.local (dockerfile)
  • .github/workflows/docker.yml (github-actions)
  • .github/workflows/gh-page.yml (github-actions)
  • .github/workflows/nodejs-tests.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.

πŸ”‘ 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 13 Pull Requests:

chore(deps): update dependency jekyll-github-metadata to v2.16.0
  • Schedule: ["at any time"]
  • Branch name: renovate/jekyll-ecosystem-packages
  • Merge into: master
  • Upgrade jekyll-github-metadata to 2.16.0
chore(deps): update dependency jekyll-toc to v0.18.0
  • Schedule: ["at any time"]
  • Branch name: renovate/jekyll-toc-0.x-lockfile
  • Merge into: master
  • Upgrade jekyll-toc to 0.18.0
chore(deps): update dependency webrick to v1.8.1
  • Schedule: ["at any time"]
  • Branch name: renovate/webrick-1.x-lockfile
  • Merge into: master
  • Upgrade webrick to 1.8.1
chore(deps): update elasticsearch docker tag to v7.17.13
  • Schedule: ["at any time"]
  • Branch name: renovate/elasticsearch-7.x
  • Merge into: master
  • Upgrade elasticsearch to 7.17.13
chore(deps): update kibana docker tag to v7.17.13
  • Schedule: ["at any time"]
  • Branch name: renovate/kibana-7.x
  • Merge into: master
  • Upgrade kibana to 7.17.13
chore(deps): update logstash docker tag to v7.17.13
  • Schedule: ["at any time"]
  • Branch name: renovate/logstash-7.x
  • Merge into: master
  • Upgrade logstash to 7.17.13
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 dependency github-pages to v228
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jekyll-ecosystem-packages
  • Merge into: master
  • Upgrade github-pages to 228
chore(deps): update dependency webpack-cli to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/webpack-cli-5.x
  • Merge into: master
  • Upgrade webpack-cli to ^5.0.0
chore(deps): update elasticsearch docker tag to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/elasticsearch-8.x
  • Merge into: master
  • Upgrade elasticsearch to 8.9.2
chore(deps): update kibana docker tag to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/kibana-8.x
  • Merge into: master
  • Upgrade kibana to 8.9.2
chore(deps): update logstash docker tag to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/logstash-8.x
  • Merge into: master
  • Upgrade logstash to 8.9.2
fix(deps): update dependency bunyan-seq to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/bunyan-seq-1.x
  • Merge into: master
  • Upgrade bunyan-seq to ^1.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.

@codecov-commenter
Copy link

Codecov Report

Patch and project coverage have no change.

Comparison is base (28cb3a1) 95.60% compared to head (911b8c6) 95.60%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #115   +/-   ##
=======================================
  Coverage   95.60%   95.60%           
=======================================
  Files          11       11           
  Lines          91       91           
=======================================
  Hits           87       87           
  Misses          4        4           

β˜” View full report in Codecov by Sentry.
πŸ“’ Have feedback on the report? Share it here.

@Ealenn Ealenn merged commit 5f2f7b1 into master Sep 16, 2023
5 checks passed
@Ealenn Ealenn deleted the renovate/configure branch September 16, 2023 15:59
@Ealenn
Copy link
Owner

Ealenn commented Sep 16, 2023

Related to #114

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

2 participants