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

Merged
merged 3 commits into from
Nov 6, 2023
Merged

chore: configure renovate #94

merged 3 commits into from
Nov 6, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 1, 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

  • .github/workflows/build.yml (github-actions)
  • .github/workflows/lint.yml (github-actions)
  • .github/workflows/release-please.yml (github-actions)
  • .github/workflows/release.yml (github-actions)
  • .github/workflows/test.yml (github-actions)
  • go.mod (gomod)
  • .github/workflows/lint.yml (regex)

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.
  • Use semantic prefixes for commit messages and PR titles.
  • Disable semantic commit scope for all commits and PR titles.
  • If Renovate detects semantic commits, it will use semantic commit type deps for all commits.
  • Enable the pre-commit manager.

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

deps: update dependency golangci/golangci-lint to v1.55.2
  • Schedule: ["at any time"]
  • Branch name: renovate/golangci-golangci-lint-1.x
  • Merge into: main
  • Upgrade golangci/golangci-lint to v1.55.2
deps: update module github.com/hashicorp/hcl/v2 to v2.19.1
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-hashicorp-hcl-v2-2.x
  • Merge into: main
  • Upgrade github.com/hashicorp/hcl/v2 to v2.19.1
deps: update module github.com/hetznercloud/hcloud-go/v2 to v2.4.0
deps: update module github.com/mitchellh/mapstructure to v1.5.0
deps: update module github.com/nywilken/go-cty to v1.13.3
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-nywilken-go-cty-1.x
  • Merge into: main
  • Upgrade github.com/nywilken/go-cty to v1.13.3
deps: update module github.com/zclconf/go-cty to v1.14.1
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-zclconf-go-cty-1.x
  • Merge into: main
  • Upgrade github.com/zclconf/go-cty to v1.14.1
deps: update module github.com/nywilken/go-cty to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-nywilken-go-cty-2.x
  • Merge into: main
  • Upgrade github.com/nywilken/go-cty to v2.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 jooola as a code owner November 1, 2023 10:33
@nywilken
Copy link
Contributor

nywilken commented Nov 1, 2023

Hi there just a quick follow up on flagged dependencies. The Packer Plugin SDK is using a fork of github.com/zclconf/go-cty at the moment due to a breaking change introduced in [email protected]. Details on the issue can be found hashicorp/packer-plugin-sdk#187

We ask that plugin maintainer ping their versions of go-cty or hcl/v2 to the version in the Packer Plugin SDK to avoid potential issues.

This is related to the two proposed PRs by renovate

  • fix(deps): update module github.com/hashicorp/hcl/v2 to v2.19.1
  • fix(deps): update module github.com/zclconf/go-cty to v1.14.1

The fork which has been updated to 1.13.3 has not been released in the SDK yet. It is slated for v0.5.2

  • chore(deps): update module github.com/nywilken/go-cty to v1.13.3

@jooola
Copy link
Member

jooola commented Nov 1, 2023

@nywilken Alright, noted, thanks for the notice.

@jooola jooola changed the title Configure Renovate chore: configure renovate Nov 3, 2023
@jooola jooola requested a review from a team as a code owner November 6, 2023 13:43
@jooola jooola force-pushed the renovate/configure branch from 83f6fd8 to 48cfa73 Compare November 6, 2023 13:49
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.

3 participants