Ignore protobuf directories

[sporkmonger]

Dependabot was trying to update dependencies inside the subtrees. Not something we want it to do.

Summary by CodeRabbit

• Chores
  • Updated dependency management configurations for pip and gomod ecosystems to enhance control over monthly updates.
  • Changed the setuptools package version from 70.0.0 to 65.5.1 for improved compatibility in the project.

[coderabbitai]

Walkthrough

The recent changes enhance dependency management by introducing new configurations for the "pip" and "gomod" ecosystems in the .github/dependabot.yml file, specifying a monthly update schedule while ignoring all dependencies. Additionally, the requirements.txt file has been updated to downgrade the setuptools package from version 70.0.0 to 65.5.1, focusing solely on this package's compatibility.

Changes

Files	Change Summary
.github/dependabot.yml	Added configurations for "pip" and "gomod" ecosystems to manage dependencies, both set to monthly updates and ignore all dependencies.
crates/ext-processor/protobuf/protoc-gen-validate/requirements.txt	Downgraded setuptools from version 70.0.0 to 65.5.1, affecting package management compatibility.

Poem

In the garden of code, where dependencies bloom,
Pip and gomod join in a monthly tune.
Setuptools took a step back in grace,
A hop and a skip, a familiar place.
Let’s celebrate changes, both big and small,
For every tweak makes our project stand tall! 🐇✨

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[dryrunsecurity]

DryRun Security Summary

The pull request primarily focuses on updating the dependency management configuration, including a security-related update to the setuptools version and the addition of Dependabot configurations to automatically update dependencies for various package ecosystems, while also ignoring all dependency updates for the Python and Go ecosystems, which should be carefully evaluated from a security perspective.

Expand for full summary

Summary:

The changes in this pull request primarily focus on updating the dependency management configuration for the project. The most notable change is the update to the setuptools version in the crates/ext-processor/protobuf/protoc-gen-validate/requirements.txt file, which is likely a security-related update to address potential vulnerabilities in older versions of setuptools.

Additionally, the changes to the .github/dependabot.yml file configure the Dependabot service to automatically update dependencies for various package ecosystems, including Cargo (Rust), GitHub Actions, Python (pip), and Go (gomod). While the changes to the Cargo and GitHub Actions configurations are straightforward, the decision to ignore all dependency updates for the Python and Go ecosystems is worth noting and should be carefully evaluated from a security perspective.

Ignoring all dependency updates, including those that may address security vulnerabilities, could potentially leave the project exposed to known issues. It's recommended to review the dependencies in the targeted directories and determine if a more selective approach to updating dependencies would be more appropriate.

Files Changed:

1. crates/ext-processor/protobuf/protoc-gen-validate/requirements.txt:

   • The setuptools version has been updated from 70.0.0 to 65.5.1, which is likely a security-related update.
   • The file contains various dependencies required for linting, building, and uploading the PGV (Protobuf Validation) Python package to PyPI.

2. .github/dependabot.yml:

   • The Cargo (Rust) dependency configuration has been updated to ignore all wasmtime* and wit-bindgen* dependencies, as well as all patch-level updates for any package.
   • The GitHub Actions dependency configuration remains unchanged, continuing to update dependencies on a weekly basis.
   • New configurations have been added for the Python (pip) and Go (gomod) package ecosystems, targeting the /crates/ext-processor/protobuf/protoc-gen-validate directory. These configurations are set to ignore all dependency updates, which should be carefully reviewed for potential security implications.

Code Analysis

We ran 9 analyzers against 2 files and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d3259b1 and a88ff32.

Files selected for processing (2)

• .github/dependabot.yml (1 hunks)
• crates/ext-processor/protobuf/protoc-gen-validate/requirements.txt (1 hunks)

Files skipped from review due to trivial changes (1)

• crates/ext-processor/protobuf/protoc-gen-validate/requirements.txt

Additional comments not posted (2)

.github/dependabot.yml (2)

21-27: LGTM! Verify the directory path for pip ecosystem.

The configuration correctly specifies a monthly update schedule and ignores all dependencies in the specified directory. Ensure that the directory path /crates/ext-processor/protobuf/protoc-gen-validate is accurate and intended.

Verification successful

---

Directory path verified successfully.

The directory /crates/ext-processor/protobuf/protoc-gen-validate exists as specified in the .github/dependabot.yml file. The configuration is correct and aligns with the intended setup. No further action is required.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the specified directory for `pip` ecosystem.

# Test: Check if the directory exists. Expect: The directory path should be valid.
fd protoc-gen-validate crates/ext-processor/protobuf

Length of output: 342

---

29-35: LGTM! Verify the directory path for gomod ecosystem.

The configuration correctly specifies a monthly update schedule and ignores all dependencies in the specified directory. Ensure that the directory path /crates/ext-processor/protobuf/protoc-gen-validate is accurate and intended.

Verification successful

---

Directory path verified successfully.

The directory /crates/ext-processor/protobuf/protoc-gen-validate specified for the gomod ecosystem in the .github/dependabot.yml file exists and is correct. No further action is needed.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the specified directory for `gomod` ecosystem.

# Test: Check if the directory exists. Expect: The directory path should be valid.
fd protoc-gen-validate crates/ext-processor/protobuf

Length of output: 342