Rust 1.97.0, FastAPI 0.140.13, GitHub Actions Security Lead Dev Stack Updates

The Rust team has announced the release of Rust 1.97.0, bringing several language improvements and new lints designed to enhance code quality and developer experience. A key highlight is the consideration of `Result<T, Uninhabited>` and `ControlFlow<Uninhabited, T>` as equivalent to `T` for the `must_use` lint. This change simplifies error handling patterns where an uninhabited type in the error variant signifies that an error state is impossible, allowing for cleaner code without unnecessary `must_use` warnings. Further enhancing code quality, Rust 1.97.0 introduces an `allow-by-default dead_code_pub_in_binary` lint. This new lint helps identify unused public items within binary crates, guiding developers to prune unnecessary code and maintain leaner, more maintainable projects. The release also includes various stabilizations and bug fixes across the compiler and standard library, contributing to the overall reliability and performance of the Rust ecosystem. Developers are encouraged to upgrade via `rustup update stable` to leverage these latest improvements.

FastAPI 0.140.13 has been released, primarily focusing on critical bug fixes for Server-Sent Events (SSE) and JSON Lines (JSONL) streaming endpoints. The most significant fix addresses an issue where the `status_code` parameter was being ignored for these streaming response types. This ensures that developers can now reliably set custom HTTP status codes for their streaming APIs, which is crucial for communicating proper response states to clients, especially in cases of errors or specific data stream conditions. In addition to the `status_code` fix, this release also includes an important update to the `format_sse_event` docstring, improving its rendering and clarity. Accurate documentation is vital for developers implementing complex streaming patterns. These updates collectively bolster FastAPI's capabilities for building robust, real-time web applications that rely on efficient and compliant streaming protocols. The FastAPI team continues to refine the framework, making it more reliable for high-performance API development.

GitHub has rolled out a significant security enhancement for GitHub Actions, introducing a new mechanism to hold potentially malicious workflows for approval. This proactive measure is designed to combat supply chain attacks where compromised GitHub credentials are used to push harmful GitHub Actions workflows, which can then steal CI/CD credentials or launch further attacks. By automatically flagging and holding such workflows, GitHub provides an essential layer of defense for public repositories, preventing unauthorized or malicious code execution. The new system directly addresses a growing vector for software supply chain vulnerabilities. When a workflow is identified as potentially malicious, it will not execute immediately but will instead enter a pending state, requiring explicit approval from repository maintainers. This gives teams a crucial window to review and verify the integrity of proposed changes before they can impact the CI/CD pipeline or compromise sensitive assets. This feature underscores GitHub's commitment to enhancing platform security and protecting the integrity of open-source and private projects alike.