RepoJournal
Rust

@rust-lang

The Rust language, Cargo, and the standard library

Pick a date

  1. Wed 20 may
  2. Thu 21 may
  3. Sat 23 may
  4. Sun 24 may
  5. Mon 25 may
  6. Tue 26 may
  7. Wed 27 may
  8. Thu 28 may
  9. Fri 29 may
  10. Sat 30 may
  11. Sun 31 may
  12. Mon 1 jun
  13. Mon 8 jun
  14. Tue 9 jun
  15. Wed 10 jun
  16. Thu 11 jun
  17. Fri 12 jun
  18. Sat 13 jun
  19. Sun 14 jun
  20. Mon 15 jun
  21. Tue 16 jun
  22. Wed 17 jun
  23. Thu 18 jun
  24. Sat 27 jun
  25. Sun 28 jun
  26. Mon 29 jun
  27. Tue 30 jun
  28. Wed 1 jul
  29. Thu 2 jul
  30. Today 3 jul

The Wire · Showcase

RUST-ANALYZER INLINE MACRO FIX LANDS, CRATES.IO DEPENDENCY SWEEP UNDERWAY

By RepoJournal · Filed · About Rust

Rust-analyzer shipped a fix that finally makes inline macro expansion work inside attribute macros and proc macro calls, ending a friction point for developers using frameworks like Tokio and esp-rtos.

The inline macro expansion [1] [2] now works in contexts where it previously failed silently - you can call inline macro from within #[tokio::main] and similar attribute macros without the tool bailing. This lands on nightly [3] and fixes a specific category of IDE frustration that hit developers frequently. Meanwhile, the crates.io ecosystem is in maintenance mode: docs.rs refreshed all lock files [14] while crates.io pushed both JavaScript [4] and Rust [5] dependency updates, with sharp bumping to 0.35.1 [6] and Storybook advancing to 10.4.4 [7]. On the documentation front, crates.io now renders Markdown definition lists properly [8], matching behavior in GitHub and GitLab. The registry index continues steady updates across ra_ap_profile [9], ra_ap_hir [11], and other toolchain crates [10] [12] [13].

Action items

References

  1. [1] fix: offer inline macro in macro call and proc macro ↗ rust-lang/rust-analyzer
  2. [2] Merge pull request #22584 from eihqnh/fix-inline-macro rust-lang/rust-analyzer
  3. [3] nightly ↗ rust-lang/rust-analyzer
  4. [4] Lock file maintenance (JS) ↗ rust-lang/crates.io
  5. [5] Lock file maintenance (Rust) ↗ rust-lang/crates.io
  6. [6] Update dependency sharp to v0.35.1 ↗ rust-lang/crates.io
  7. [7] Update storybook monorepo to v10.4.4 ↗ rust-lang/crates.io
  8. [8] Render Markdown definition lists ↗ rust-lang/crates.io
  9. [9] Update crate `ra_ap_profile` rust-lang/crates.io-index
  10. [10] Update crate `bamboo-sdk` rust-lang/crates.io-index
  11. [11] Update crate `ra_ap_hir` rust-lang/crates.io-index
  12. [12] Update crate `formatx` rust-lang/crates.io-index
  13. [13] Update crate `bamboo-engine` rust-lang/crates.io-index
  14. [14] chore(deps): lock file maintenance lockfile maintenance ↗ rust-lang/docs.rs

FAQ

What changed in Rust on June 15, 2026?
Rust-analyzer shipped a fix that finally makes inline macro expansion work inside attribute macros and proc macro calls, ending a friction point for developers using frameworks like Tokio and esp-rtos.
What should Rust teams do about it?
Review and merge crates.io lock file PRs [ref:17] [ref:18] when ready - routine but not urgent • Test inline macro expansion with your tokio and esp-rtos code on nightly [ref:10] • Verify sharp 0.35.1 compatibility in crates.io frontend tests [ref:20]
Which Rust repositories shipped on June 15, 2026?
rust-lang/rust-analyzer, rust-lang/crates.io, rust-lang/crates.io-index, rust-lang/docs.rs

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.