Skip to content

deps(deps): bump toml from 1.0.0+spec-1.1.0 to 1.0.1+spec-1.1.0 in the cargo-minor-patch group - #96

Merged
github-actions[bot] merged 2 commits into
mainfrom
dependabot/cargo/cargo-minor-patch-35e1db9230
Feb 13, 2026
Merged

deps(deps): bump toml from 1.0.0+spec-1.1.0 to 1.0.1+spec-1.1.0 in the cargo-minor-patch group#96
github-actions[bot] merged 2 commits into
mainfrom
dependabot/cargo/cargo-minor-patch-35e1db9230

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Feb 13, 2026

Copy link
Copy Markdown
Contributor

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.


Bumps the cargo-minor-patch group with 1 update: toml.

Updates toml from 1.0.0+spec-1.1.0 to 1.0.1+spec-1.1.0

Commits
  • 767747f chore: Release
  • c68aa87 fix(parser): Plug another whole in synthetic events (#1102)
  • 17dc3dd fix(parser): Plug another whole in synthetic events
  • 0f32a02 test(parse): Add another test case
  • 9fef741 docs: Update changelog
  • 3c59611 fix(edit): Remove panics on bad input (#1101)
  • 7968120 fix(edit): On missing value, ensure a span is used
  • b91d460 fix(edit): Don't panic on inline table keys without values
  • c8087a6 fix(parser): Improve unclosed array messages
  • f0a47d4 fix(parser): Improve unclosed inline table messages
  • Additional commits viewable in compare view

Dependabot compatibility score

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the cargo-minor-patch group with 1 update: [toml](https://github.com/toml-rs/toml).


Updates `toml` from 1.0.0+spec-1.1.0 to 1.0.1+spec-1.1.0
- [Commits](toml-rs/toml@toml-v1.0.0...toml-v1.0.1)

---
updated-dependencies:
- dependency-name: toml
  dependency-version: 1.0.1+spec-1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Feb 13, 2026
@coderabbitai

coderabbitai Bot commented Feb 13, 2026

Copy link
Copy Markdown

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.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch dependabot/cargo/cargo-minor-patch-35e1db9230

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
github-actions Bot enabled auto-merge (squash) February 13, 2026 17:32
@github-actions
github-actions Bot merged commit 9a366c9 into main Feb 13, 2026
1 check passed
@qodo-code-review

qodo-code-review Bot commented Feb 13, 2026

Copy link
Copy Markdown
Contributor

PR-Agent failed to apply 'local' repo settings

The configuration file needs to be a valid TOML, please fix it.


Error message:
cannot access local variable 'file_data' where it is not associated with a value

Configuration content:
# Qodo Merge (PR-Agent) — MCB repository configuration
# ALL features enabled at maximum thoroughness.
# Full reference: https://github.com/qodo-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml

# ===========================================================================
# Core Settings
# ===========================================================================
[config]
response_language = "en-US"
output_relevant_configurations = true
add_repo_metadata = true
reasoning_effort = "high"

# ===========================================================================
# GitHub App — Triggers & Commands
# ===========================================================================
[github_app]
handle_pr_actions = ['opened', 'reopened', 'ready_for_review']
pr_commands = [
    "/describe --pr_description.final_update_message=false",
    "/review --pr_reviewer.num_max_findings=7",
    "/improve --pr_code_suggestions.commitable_code_suggestions=true",
]
handle_push_trigger = true
push_commands = [
    "/describe --pr_description.final_update_message=false",
    "/review --pr_reviewer.num_max_findings=5",
]

# ===========================================================================
# /review — Code Review
# ===========================================================================
[pr_reviewer]
require_score_review = true
require_tests_review = true
require_estimate_effort_to_review = true
require_can_be_split_review = true
require_security_review = true
require_ticket_analysis_review = true
require_todo_scan = true
num_max_findings = 7
persistent_comment = true
enable_review_labels_security = true
enable_review_labels_effort = true
enable_help_text = true
extra_instructions = """\
You are reviewing a Rust 2024 edition workspace (9 crates) that follows Clean Architecture.

Architecture rules (CI-blocking):
- Dependencies point inward only: mcb-server -> mcb-infrastructure -> mcb-application -> mcb-domain
- mcb-providers implements port traits from mcb-domain, registers via linkme distributed slices
- mcb-domain has ZERO dependencies on other MCB crates
- No direct imports from mcb-providers in mcb-server (use DI via mcb-infrastructure)

Safety (workspace lints — deny):
- unsafe_code is denied. Flag any unsafe block.
- Flag unwrap()/expect() outside of test modules. Use ? and Result propagation.
- Flag todo!()/unimplemented!() in non-draft code.
- Flag empty catch / error-swallowing patterns.

Multi-tenancy rules (critical):
- NEVER hardcode org_id / DEFAULT_ORG_ID in handler code.
- Tenant context must come from request context or OrgContext::default().
- Error responses must NOT leak internal details (DB errors, file paths, stack traces).
- All new handlers MUST have tracing instrumentation.

Patterns to enforce:
- New providers MUST register via #[linkme::distributed_slice] with function pointers (not closures).
- Error types use thiserror in domain, anyhow in application orchestration.
- Async traits use #[async_trait] from the async-trait crate.
- Services consume ports as Arc<dyn Trait>, never concrete provider types.
- Import order: std -> external crates -> workspace crates (mcb_*) -> local modules.
- Max line width: 100 chars (rustfmt.toml).
- New logic MUST include tests.
- Build commands use make targets, not raw cargo.
"""

# ===========================================================================
# /describe — PR Description
# ===========================================================================
[pr_description]
publish_labels = true
add_original_user_description = true
generate_ai_title = false
use_bullet_points = true
enable_pr_type = true
enable_semantic_files_types = true
collapsible_file_list = 'adaptive'
collapsible_file_list_threshold = 8
enable_pr_diagram = true
enable_large_pr_handling = true
inline_file_summary = 'table'
max_ai_calls = 4
async_ai_calls = true

# ===========================================================================
# /improve — Code Suggestions
# ===========================================================================
[pr_code_suggestions]
commitable_code_suggestions = true
focus_only_on_problems = true
persistent_comment = true
suggestions_score_threshold = 3
dual_publishing_score_threshold = 7
auto_extended_mode = true
num_code_suggestions_per_chunk = 4
num_best_practice_suggestions = 2
demand_code_suggestions_self_review = true
publish_post_process_suggestion_impact = true
wiki_page_accepted_suggestions = true
allow_thumbs_up_down = true
apply_suggestions_checkbox = true
self_reflect_on_suggestions = true
extra_instructions = """\
For this Rust project, focus suggestions on:
- Missing error propagation (unwrap/expect outside tests)
- Architecture boundary violations (wrong crate importing another)
- Missing or inadequate tests for new logic
- Potential performance issues (unnecessary clones, allocations in hot paths)
- Security concerns (input validation, credential handling, leaky error messages)
- Multi-tenant isolation violations (hardcoded org_id, missing tenant scoping)
Do NOT suggest style changes already handled by rustfmt (formatting, whitespace).
"""

# ===========================================================================
# /improve — Self-Reflection
# ===========================================================================
[pr_code_suggestions.self_reflect_on_suggestions]
enabled = true

# ===========================================================================
# Auto Best Practices — Learning from PR history
# ===========================================================================
[auto_best_practices]
enable_auto_best_practices = true
utilize_auto_best_practices = true
max_patterns = 7
extra_instructions = """\
Pay special attention to patterns involving:
- Clean Architecture boundary enforcement
- linkme distributed slice registration
- Error handling with thiserror/anyhow
- Multi-tenant data isolation
"""

# ===========================================================================
# Best Practices — Static Rules
# ===========================================================================
[best_practices]
content = """\
## MCB Rust Best Practices

### Architecture
- Follow Clean Architecture: domain -> application -> infrastructure -> server
- Port traits in mcb-domain, adapters in mcb-providers
- Provider registration via linkme distributed slices
- DI via dill IoC container (ADR-029)
- Config via figment (ADR-025)

### Safety
- No unsafe code (workspace lint: deny)
- No unwrap()/expect() outside tests
- Use Result<T, Error> with thiserror/anyhow
- Helper constructors for errors: Error::io(), Error::config()

### Multi-Tenancy
- Every query MUST be scoped by org_id
- Never hardcode DEFAULT_ORG_ID in handler logic
- Use OrgContext from request context / auth token
- Error responses MUST NOT leak internal details (DB errors, file paths)

### Testing
- Unit tests in crates/*/tests/unit/
- Integration tests in crates/*/tests/integration.rs
- Golden acceptance tests in tests/golden/
- Use #[tokio::test] for async, tempfile for filesystem tests

### Build System
- Always use make targets: make build, make test, make lint, make validate
- CI pipeline: lint -> test -> startup-smoke -> validate -> audit -> docs

### Commits
- Conventional commits: feat|fix|docs|refactor(scope): description
- Scope = module or crate name

### Observability
- All handlers annotated with #[tracing::instrument]
- Use tracing::info!/warn!/error! for structured logging
- Include org_id, project_id in span fields
"""

@dependabot
dependabot Bot deleted the dependabot/cargo/cargo-minor-patch-35e1db9230 branch February 13, 2026 20:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant