Bump prost from 0.11.9 to 0.13.3

[dependabot]

Bumps prost from 0.11.9 to 0.13.3.

Changelog

Sourced from prost's changelog.

Prost version 0.13.3

PROST! is a Protocol Buffers implementation for the Rust Language. prost generates simple, idiomatic Rust code from proto2 and proto3 files.

Features

• (prost-types) Add normalized functions (#1158)

Bug Fixes

• (prost-build) Remove derived(Copy) on boxed fields (#1157)

Documentation

• (prost-types) Add description of using Any (#1141)
• (prost-build) Use cargo add in example (#1149)

Styling

• Use Path::display() when printing a path (#1150)
• MessageGraph::new() can't actually fail (#1151)
• (generated-code) Use Self in as_str_name (#1154)

Testing

• Actually test skip_debug for prost::Oneof (#1148)
• (prost-build) Validate error texts (#1152)
• (prost-build) Fix error texts (#1156)

Build

• Increase MSRV to 1.71.1 (#1135)
• (deps) Update pulldown-cmark to 0.12 and pulldown-cmark-to-cmark to 16 (#1144)
• (protobuf) Compile and install protoc on Windows (#1145)
• (protobuf) Use same protoc from same repo as .proto-files (#1136)
• (deps) Update pulldown-cmark-to-cmark from 16 to 17 (#1155)
• Unify assert on fixtures (#1142)

Prost version 0.13.2

PROST! is a Protocol Buffers implementation for the Rust Language. prost generates simple, idiomatic Rust code from proto2 and proto3 files.

Features

• prost-build: Add protoc executable path to Config (#1126)
• prost-build: Extract file descriptor loading from compile_protos() (#1067)

Bug Fixes

... (truncated)

Commits

• 9ed944e chore: Release version 0.13.3 (#1164)
• fb977f4 fix(prost-build): Remove derived(Copy) on boxed fields (#1157)
• 8d4cac5 feat(prost-types): Add normalized functions (#1158)
• 644c328 build(deps): update pulldown-cmark-to-cmark from 16 to 17 (#1155)
• 4b1b982 style(generated-code): use Self in as_str_name (#1154)
• 9fa3f2e tests(prost-build): Fix error texts (#1156)
• 7dcd269 tests(prost-build): Validate error texts (#1152)
• d3fd54c style: MessageGraph::new() can't actually fail (#1151)
• d059d05 style: use Path::display() when printing a path (#1150)
• 18c4681 docs(prost-build): Use cargo add in example (#1149)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

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.

[dryrunsecurity]

DryRun Security Summary

The provided code changes primarily involve updating the versions of several dependencies, including prost, itertools, and windows-targets, in the crates/ext-processor/Cargo.toml file and the corresponding Cargo.lock file, which are generally benign and do not raise any immediate security concerns, but it's important to review the release notes and changelogs of the updated dependencies to ensure there are no known security vulnerabilities or breaking changes.

Expand for full summary

Summary:

The provided code changes primarily involve updating the versions of several dependencies in the crates/ext-processor/Cargo.toml file and the corresponding Cargo.lock file. These updates include the prost, itertools, and windows-targets dependencies.

From an application security perspective, these changes are generally benign and do not raise any immediate security concerns. Dependency version updates are a common practice and often include bug fixes, performance improvements, or new features. However, it's important to review the release notes and changelogs of the updated dependencies to ensure that there are no known security vulnerabilities or breaking changes that could impact the application.

As a best practice, it's recommended to have a robust dependency management process in place, where dependencies are regularly reviewed and updated to the latest stable versions, and any security advisories or vulnerabilities are promptly addressed. This helps maintain the security and integrity of the application over time.

Files Changed:

1. crates/ext-processor/Cargo.toml: The changes in this file update the version of the prost dependency from ^0.11 to ^0.13. This is a minor version update and is generally a positive change, but it's still important to review the release notes and changelog to ensure there are no known security vulnerabilities or breaking changes.

2. Cargo.lock: The changes in this file indicate that several dependencies have been updated, including:

   • itertools from version 0.10.5 to 0.12.1
   • prost from version 0.11.9 to 0.13.3
   • windows-targets from version 0.48.5 to 0.52.5
     These updates are generally positive, but it's recommended to review the release notes and changelogs for any potential security implications.

Code Analysis

We ran 9 analyzers against 2 files and 0 analyzers had findings. 9 analyzers had no findings.

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.