{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigpxc6jedo4btjkqgod5pw5i5t2p3rgoiteuvdaeykze7mrwko2ve",
    "uri": "at://did:plc:lujatorbzcq2chhxnvjgc464/app.bsky.feed.post/3mepfew3s7rj2"
  },
  "path": "/2026/02/12/Rust-1.93.1/",
  "publishedAt": "2026-02-12T00:00:00.000Z",
  "site": "https://blog.rust-lang.org",
  "tags": [
    "get `rustup`",
    "Don't try to recover a keyword as a non-keyword identifier",
    "affected rustfmt",
    "Fix a `clippy::panicking_unwrap` false-positive on field access with an implicit dereference",
    "Revert an update to wasm-related dependencies",
    "Thanks!"
  ],
  "textContent": "The Rust team has published a new point release of Rust, 1.93.1. Rust is a programming language that is empowering everyone to build reliable and efficient software.\n\nIf you have a previous version of Rust installed via rustup, getting Rust 1.93.1 is as easy as:\n\n\n    rustup update stable\n\nIf you don't have it already, you can get `rustup` from the appropriate page on our website.\n\n##  What's in 1.93.1\n\nRust 1.93.1 resolves three regressions that were introduced in the 1.93.0 release.\n\n  * Don't try to recover a keyword as a non-keyword identifier, fixing an internal compiler error (ICE) that especially affected rustfmt.\n\n  * Fix a `clippy::panicking_unwrap` false-positive on field access with an implicit dereference.\n\n  * Revert an update to wasm-related dependencies, fixing file descriptor leaks on the `wasm32-wasip2` target. This only affects the `rustup` component for this target, so downstream toolchain builds should check their own dependencies too.\n\n\n\n\n###  Contributors to 1.93.1\n\nMany people came together to create Rust 1.93.1. We couldn't have done it without all of you. Thanks!",
  "title": "Announcing Rust 1.93.1",
  "updatedAt": "2026-02-12T00:00:00.000Z"
}