build(deps): update Tokio to 1.53.2 in Tauri lockfile

Merged
QN
2d ago
+4-2

User description

Change

  • Update only src-tauri/Cargo.lock: Tokio 1.53.1 to 1.53.2, matching Dependabot PR #1044.
  • crates.io metadata confirms the published checksum and Rust 1.71 minimum; the repository's Rust 1.77.2 floor is preserved.
  • No source code, manifest, updater pin, release, or production setting changes are included.

Validation

  • Signed commit verified locally.
  • PR_BUDGET_BASE=origin/main pnpm run ci:prepush passed; full PR CI and resulting-main qualification remain required.

Cohort and retention

  • This is one narrow integration unit in the owner-authorized frozen Dependabot cohort recorded in #927.
  • Original bot PR #1044 remains open until this replacement is merged and the exact resulting-main gates pass.
  • The bounded train has 0 merges so far; the 12-merge/24-hour ceiling and mandatory Production checks remain in force. Vercel platform writes remain 0; the Claude-only writer is unchanged.

Summary by Sourcery

Refresh the Tauri dependency lockfile to Tokio 1.53.2 without changing application source or package manifests.

Build:

  • Update the Tauri lockfile to Tokio 1.53.2.

Documentation:

  • Document the Tokio dependency update in the unreleased changelog.

Summary by cubic

Updates Tokio to 1.53.2 in src-tauri/Cargo.lock, matching Dependabot PR #1044 without source code changes, and records the change in the CHANGELOG.

  • Preserves the Rust 1.77.2 floor while adopting the published crate checksum.
  • Local prepush checks pass; full CI and resulting-main qualification remain required.
  • Original bot PR #1044 stays open until this replacement merges.

Summary by CodeRabbit

  • Chores
    • Updated an underlying runtime component to a newer patch version.
  • User-facing changes
    • No changes to app features or behavior are included in this update.

CodeAnt-AI Description

Update Tokio to 1.53.2 for Tauri builds

What Changed

  • Tauri’s locked Tokio version is updated from 1.53.1 to 1.53.2.
  • The changelog records the update; application source and package manifests are unchanged.

Impact

✅ Tauri builds resolve Tokio 1.53.2
✅ No application behavior changes

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.