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

Merged
merged 1 commit into from
Oct 2, 2021
Merged

Configure Renovate #56

merged 1 commit into from
Oct 2, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 21, 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

  • .github/workflows/terraform.yml (github-actions)
  • package.json (npm)
  • versions.tf (terraform)

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 semantic commits detected, 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 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
  • Use node versioning for @types/node
  • Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133

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

chore(deps): pin dependencies
chore(deps): update actions/github-script action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-github-script-5.x
  • Merge into: master
  • Upgrade actions/github-script to v5
chore(deps): update commitlint monorepo to v13 (major)
chore(deps): update dependency husky to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/husky-7.x
  • Merge into: master
  • Upgrade husky to 7.0.2
chore(deps): update terraform http to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/http-2.x
  • Merge into: master
  • Upgrade http to ~> 2.0
chore(deps): update terraform null to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/null-3.x
  • Merge into: master
  • Upgrade null to ~> 3.0
chore(deps): update terraform random to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/random-3.x
  • Merge into: master
  • Upgrade random to ~> 3.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 WhiteSource Renovate. View repository job log here.

@github-actions
Copy link
Contributor

Terraform Init success

Terraform Validate success

Terraform Plan failure

Show Plan
Error: unable to authenticate (unauthorized)

  with data.hcloud_image.ubuntu,
  on main.tf line 20, in data "hcloud_image" "ubuntu":
  20: data "hcloud_image" "ubuntu" {

Pusher: @renovate[bot], Action: pull_request, Workdir: examples/hcloud-k3s, Workflow: Terraform GitHub Actions

@xunleii xunleii merged commit b0e94ad into master Oct 2, 2021
@xunleii xunleii deleted the renovate/configure branch October 2, 2021 07:51
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.

2 participants