Skip to content
This repository has been archived by the owner on Jan 11, 2022. It is now read-only.

Configure Renovate #1

Closed
wants to merge 1 commit into from
Closed

Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 9, 2021

WhiteSource 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

  • .circleci/config.yml (circleci)
  • .github/workflows/main.yml (github-actions)
  • .github/workflows/semver-check.yaml (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
  • Separate major versions of dependencies into individual branches/PRs
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs immediately (after branch is created)
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • 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 20 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings
  • Ignore spring cloud 1.x releases
  • Ignore http4s digest-based 1.x milestones

🔡 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 8 Pull Requests:

chore(deps): update dependency @​adobe/helix-deploy to v3.18.6
  • Schedule: ["at any time"]
  • Branch name: renovate/adobe-helix-deploy-3.x
  • Merge into: main
  • Upgrade @adobe/helix-deploy to 3.18.6
chore(deps): update dependency eslint to v7.24.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-7.x
  • Merge into: main
  • Upgrade eslint to 7.24.0
fix(deps): update dependency @​adobe/helix-shared to v7.25.0
  • Schedule: ["at any time"]
  • Branch name: renovate/adobe-helix-shared-7.x
  • Merge into: main
  • Upgrade @adobe/helix-shared to 7.25.0
fix(deps): update dependency @​adobe/helix-status to v9.1.6
  • Schedule: ["at any time"]
  • Branch name: renovate/adobe-helix-status-9.x
  • Merge into: main
  • Upgrade @adobe/helix-status to 9.1.6
fix(deps): update dependency @​adobe/openwhisk-action-logger to v2.4.4
fix(deps): update dependency @​adobe/openwhisk-action-utils to v4.4.4
  • Schedule: ["at any time"]
  • Branch name: renovate/adobe-openwhisk-action-utils-4.x
  • Merge into: main
  • Upgrade @adobe/openwhisk-action-utils to 4.4.4
chore(deps): update dependency @​adobe/helix-deploy to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/adobe-helix-deploy-4.x
  • Merge into: main
  • Upgrade @adobe/helix-deploy to 4.0.1
chore(deps): update helix-post-deploy orb to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/helix-post-deploy-2.x
  • Merge into: main
  • Upgrade helix-post-deploy to 2.0.10

🚸 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 WhiteSource Renovate. View repository job log here.

@github-actions
Copy link

github-actions bot commented Apr 9, 2021

This PR will trigger no release when merged.

@codecov
Copy link

codecov bot commented Apr 9, 2021

Codecov Report

Merging #1 (0f4af2e) into main (ff6c04b) will not change coverage.
The diff coverage is n/a.

❗ Current head 0f4af2e differs from pull request most recent head c04fdfb. Consider uploading reports for the commit c04fdfb to get more accurate results
Impacted file tree graph

@@            Coverage Diff            @@
##              main        #1   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         2    -2     
  Lines           50        22   -28     
=========================================
- Hits            50        22   -28     
Impacted Files Coverage Δ
src/index.js 100.00% <0.00%> (ø)
src/utils.js 100.00% <0.00%> (ø)
src/vcl-utils.js
src/updateredirects.js

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ff6c04b...c04fdfb. Read the comment docs.

@renovate renovate bot force-pushed the renovate/configure branch 7 times, most recently from af1bd8a to a2d6217 Compare April 13, 2021 09:35
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants