
Infrastructure Eng @rust_foundation ποΈ Podcast https://xitter.cf/t.co/Tvh32Pcxkl π¦ Automating Rust releases @release_plz_dev π @MarcoIeni@hachyderm.io
Messina, Italy
Joined April 2020
- Tweets1.3K
- Following406
- Followers2.3K
- Likes1.6K
Great to see companies investing in making easier to ship Rust apps!
Millions of developers use Rust, and keeping its infrastructure running takes constant effort.
We talked to @marcoieni from the @rust_foundation about CI costs, security, the shortage of reviewers, and the challenges of maintaining Rust's infrastructure.
serokell.io/blog/the-hidden-β¦
TDD: Twitter Driven Development
Marco Ieni π¦ retweeted
Introducing tsrs: a Rust port of the TypeScript compiler π¦
We are not forking TypeScript!
β In close collaborating with the TypeScript team
β Up to 8x faster than TS 7.0 & ~70% less memory
β Runs in WASM, so it works in your browser & on Workers
β Soon part of the Oxc toolchain
npx tsrs
blog.cloudflare.com/typescriβ¦
Clippy has a new homepage!
π Goodbye rust-lang.github.io/rust-cliβ¦
π Welcome clippy.rust-lang.org/
Marco Ieni π¦ retweeted
Cargo's compilation model is built around crates: independent crates get compiled in parallel, and unaffected crates can be skipped entirely.
We split up uv's primary crate into 14 (!) crates (from 46k to 6k lines of code), and it sped up incremental build times by 30 to 40%!
Thanks @encoredotdev for sponsoring @release_plz_dev !
The release-plz GitHub Action is now used by 3600 public GitHub projects.
Great to see a company finally recognizing my efforts π
Btw if you want to deploy your app and you don't want to deal with Terraform, check them out!
Encore is now a proud sponsor of release-plz / @marcoieni.
(Part of our ongoing effort to support the open-source projects and people we build on)
Here is a cool video showcasing how @encoredotdev works: xitter.cf/encoredotdev/status/21β¦
Here is what the #rustlang Infrastructure Team worked on in the last three months and what we want to do next
blog.rust-lang.org/inside-ruβ¦
Marco Ieni π¦ retweeted
rust tools deserve good trailers too π¦
Result of something similar to this (CI failed on main because it didn't finish in time for the next commit. I need to setup a merge queue).
1. Ask AI to open a draft PR to add benchmarks for your projects, covering the most common use cases.
2. Don't review that PR.
3. Ask AI to spawn subagents to use these benchmarks to identify up to 10 performance wins that are easy to review and open a PR for each of them.
Since Rust 1.99.0 there's no need to set CARGO_INCREMENTAL=0 in CI.
doc.rust-lang.org/beta/cargoβ¦
Iβm now team leader of the Rust Infrastructure team!
Iβll keep shipping, but Iβll also pay more attention to the load, health, and overall direction of the team.
My stream deck plugin for the ChatGPT Desktop App is available in the Elgato marketplace (free and open source)! πββ¬
marketplace.elgato.com/produβ¦
My favorite features: seeing the progress of the chats on the device and clicking their button to open them in the App.
I changed the Pull Request template of release-plz.
I realized I don't care if you used AI to write code, or how you used AI, or which model you used.
I just want to make sure you reviewed the code before submitting it. π§΅
This is the most sustainable way I found to keep maintaining release-plz in my spare time.
It seems like it's working. In the last month:
- 39 PRs merged in main excluding automations such as renovate.
- closed 18 issues. Lots of bug fixes!








![Graph showing weekly GitHub commits from December 2021 to October 2026, highlighting contributors 'marcoieni' and 'renovate[bot]'. https://github.com/release-plz/release-plz/graphs/contributors?from=12%2F1%2F2021&to=10%2F4%2F2026
Marco authored 1360 commits.](https://pbs.twimg.com/media/HULjnBgaQAE0ufV.jpg?name=small&format=webp)





