Skip to content

Weekly cargo update of primary dependencies - #998

Merged
github-actions[bot] merged 1 commit into
mainfrom
main_cargo_update
Oct 19, 2026
Merged

github-actions[bot] merged 1 commit into
mainfrom
main_cargo_update

Conversation

@obi1kenobi

Copy link
Copy Markdown
Owner

Automation to keep dependencies in the primary Cargo.lock current.

The following is the output from cargo update:

     Locking 24 packages to highest Rust 1.91 compatible versions as of 7 days ago
    Updating cc v1.6.0 -> v1.8.0
    Updating either v1.18.0 -> v1.19.0
    Updating h2 v0.4.19 -> v0.4.20
    Updating hyper v1.11.1 -> v1.12.0
    Updating pest v2.9.2 -> v2.9.3 (available: v2.9.4, published 3 days ago)
    Updating powerfmt v0.2.0 -> v0.2.1
      Adding psm v0.1.24 (available: v0.1.32)
    Updating serde_json v1.0.151 -> v1.0.154
    Updating serde_spanned v1.1.1 -> v1.1.2
    Updating smallvec v1.16.2 -> v1.16.3
      Adding stacker v0.1.25
    Updating syn v3.0.6 -> v3.0.8 (available: v3.0.9, published 7 days ago)
    Updating tokio-util v0.7.19 -> v0.7.20
    Updating toml v1.1.6+spec-1.1.0 -> v1.1.8+spec-1.1.0
    Updating toml_datetime v1.1.1+spec-1.1.0 -> v1.1.2+spec-1.1.0
    Updating toml_parser v1.1.3+spec-1.1.0 -> v1.1.5+spec-1.1.0
    Updating toml_writer v1.1.2+spec-1.1.0 -> v1.1.3+spec-1.1.0
    Updating trybuild v1.0.121 -> v1.0.122
    Updating unicase v2.9.0 -> v2.10.0
    Updating uuid v1.27.0 -> v1.28.0
    Updating want v0.3.1 -> v0.3.2
    Updating zerocopy v0.8.59 -> v0.8.62 (available: v0.8.63, published 5 days ago)
    Updating zerocopy-derive v0.8.59 -> v0.8.62 (available: v0.8.63, published 5 days ago)
    Updating zeroize v1.9.0 -> v1.9.1
note: pass `--verbose` to see 19 unchanged dependencies behind latest

     Locking 24 packages to highest Rust 1.91 compatible versions as of 7 days ago
    Updating cc v1.6.0 -> v1.8.0
    Updating either v1.18.0 -> v1.19.0
    Updating h2 v0.4.19 -> v0.4.20
    Updating hyper v1.11.1 -> v1.12.0
    Updating pest v2.9.2 -> v2.9.3 (available: v2.9.4, published 3 days ago)
    Updating powerfmt v0.2.0 -> v0.2.1
      Adding psm v0.1.24 (available: v0.1.32)
    Updating serde_json v1.0.151 -> v1.0.154
    Updating serde_spanned v1.1.1 -> v1.1.2
    Updating smallvec v1.16.2 -> v1.16.3
      Adding stacker v0.1.25
    Updating syn v3.0.6 -> v3.0.8 (available: v3.0.9, published 7 days ago)
    Updating tokio-util v0.7.19 -> v0.7.20
    Updating toml v1.1.6+spec-1.1.0 -> v1.1.8+spec-1.1.0
    Updating toml_datetime v1.1.1+spec-1.1.0 -> v1.1.2+spec-1.1.0
    Updating toml_parser v1.1.3+spec-1.1.0 -> v1.1.5+spec-1.1.0
    Updating toml_writer v1.1.2+spec-1.1.0 -> v1.1.3+spec-1.1.0
    Updating trybuild v1.0.121 -> v1.0.122
    Updating unicase v2.9.0 -> v2.10.0
    Updating uuid v1.27.0 -> v1.28.0
    Updating want v0.3.1 -> v0.3.2
    Updating zerocopy v0.8.59 -> v0.8.62 (available: v0.8.63, published 5 days ago)
    Updating zerocopy-derive v0.8.59 -> v0.8.62 (available: v0.8.63, published 5 days ago)
    Updating zeroize v1.9.0 -> v1.9.1
note: pass `--verbose` to see 19 unchanged dependencies behind latest
@obi1kenobi obi1kenobi added the R-automated Release: these changes were created automatically by a bot label Oct 19, 2026
@github-actions
github-actions Bot enabled auto-merge (squash) October 19, 2026 03:51
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-19T03:54:01.857556Z e8dfdf3 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e8dfdf33b7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread Cargo.lock
[[package]]
name = "pest"
version = "2.9.2"
version = "2.9.3"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Avoid pest 2.9.3 on musllinux parsing paths

When the published musllinux wheel invokes Schema::parse() or interpret_query() with less than 64 KiB of stack reported as remaining, this pest release rejects even trivial valid GraphQL with stack limit reached: pest 2.9.3 introduced an unconditional 64 KiB check through stacker::remaining_stack() in std builds (upstream implementation). This is especially problematic for the explicitly supported musllinux wheels in .github/workflows/publish-python.yml:350-373, where main-thread stack-bound reporting can leave less than that threshold after Python host frames. Pin to a release without this false-positive behavior or add a verified workaround before shipping these wheels.

Useful? React with 👍 / 👎.

@github-actions
github-actions Bot merged commit bd6f04b into main Oct 19, 2026
22 checks passed
@github-actions
github-actions Bot deleted the main_cargo_update branch October 19, 2026 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

R-automated Release: these changes were created automatically by a bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant