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

Closed
wants to merge 1 commit into from
Closed

chore: Configure Renovate #995

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 8, 2024

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/benchmarks.yml (github-actions)
  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/codeql.yml (github-actions)
  • .github/workflows/goreleaser.yml (github-actions)
  • .github/workflows/lint-pr.yml (github-actions)
  • .github/workflows/lint.yml (github-actions)
  • .github/workflows/pr-reminder.yml (github-actions)
  • cmd/go.mod (gomod)
  • cmd/legacydump/go.mod (gomod)
  • go.mod (gomod)
  • v2/go.mod (gomod)
  • v2/migrate/go.mod (gomod)

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 (except for nuget) 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 18 Pull Requests:

fix(deps): update github.com/syndtr/goleveldb digest to 126854a
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-syndtr-goleveldb-digest
  • Merge into: master
  • Upgrade github.com/syndtr/goleveldb to 126854af5e6d8295ef8e8bee3040dd8380ae72e8
fix(deps): update golang.org/x/exp digest to 225e2ab
  • Schedule: ["at any time"]
  • Branch name: renovate/golang.org-x-exp-digest
  • Merge into: master
  • Upgrade golang.org/x/exp to 225e2abe05e6
chore(deps): update dependency go to v1.23.2
  • Schedule: ["at any time"]
  • Branch name: renovate/go-1.x
  • Merge into: master
  • Upgrade go to 1.23.2
fix(deps): update module cosmossdk.io/api to v0.7.6
  • Schedule: ["at any time"]
  • Branch name: renovate/cosmossdk.io-api-0.x
  • Merge into: master
  • Upgrade cosmossdk.io/api to v0.7.6
fix(deps): update module github.com/cosmos/cosmos-db to v1.0.2
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-cosmos-cosmos-db-1.x
  • Merge into: master
  • Upgrade github.com/cosmos/cosmos-db to v1.0.2
fix(deps): update module github.com/cosmos/iavl to v0.21.1
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-cosmos-iavl-0.x
  • Merge into: master
  • Upgrade github.com/cosmos/iavl to v0.21.1
fix(deps): update module github.com/cosmos/iavl/v2 to v2.0.0-20241002164643-1ddbc26b5bd1
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-cosmos-iavl-v2-2.x
  • Merge into: master
  • Upgrade github.com/cosmos/iavl/v2 to 1ddbc26b5bd1
fix(deps): update module github.com/emicklei/dot to v1.6.2
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-emicklei-dot-1.x
  • Merge into: master
  • Upgrade github.com/emicklei/dot to v1.6.2
fix(deps): update module github.com/kocubinski/costor-api to v1.1.2
fix(deps): update module cosmossdk.io/log to v1.4.1
  • Schedule: ["at any time"]
  • Branch name: renovate/cosmossdk.io-log-1.x
  • Merge into: master
  • Upgrade cosmossdk.io/log to v1.4.1
fix(deps): update module github.com/cometbft/cometbft-db to v0.15.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-cometbft-cometbft-db-0.x
  • Merge into: master
  • Upgrade github.com/cometbft/cometbft-db to v0.15.0
fix(deps): update module github.com/prometheus/client_golang to v1.20.4
fix(deps): update module github.com/rs/zerolog to v1.33.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-rs-zerolog-1.x
  • Merge into: master
  • Upgrade github.com/rs/zerolog to v1.33.0
fix(deps): update module github.com/spf13/cobra to v1.8.1
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-spf13-cobra-1.x
  • Merge into: master
  • Upgrade github.com/spf13/cobra to v1.8.1
fix(deps): update module github.com/stretchr/testify to v1.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-stretchr-testify-1.x
  • Merge into: master
  • Upgrade github.com/stretchr/testify to v1.9.0
chore(deps): update goreleaser/goreleaser-action action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/goreleaser-goreleaser-action-6.x
  • Merge into: master
  • Upgrade goreleaser/goreleaser-action to v6
fix(deps): update module github.com/cometbft/cometbft-db to v1
fix(deps): update module github.com/cosmos/iavl to v1.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-cosmos-iavl-1.x
  • Merge into: master
  • Upgrade github.com/cosmos/iavl to v1.3.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.


Warning

Please correct - or verify that you can safely ignore - these dependency lookup failures before you merge this PR.

  • Could not determine new digest for update (go package cosmossdk.io/core)

Files affected: cmd/go.mod


❓ 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner October 8, 2024 09:26
Copy link

coderabbitai bot commented Oct 8, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@julienrbrt
Copy link
Member

Not needed as per @auricom

@julienrbrt julienrbrt closed this Oct 8, 2024
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.

1 participant