https://meet.jit.si/CargoTeamMeeting Label issues or PRs with I-nominated-to-discuss to add them to the agenda. FCP/Nominated/RFC Status Overview 2025-04-22 Improved handling of non-writable rlib/rmeta fileshttps://github.com/rust-lang/cargo/issues/12674 -Zgc: Using atime for being more resilient with older cargoes.

Performance Roadmap Discuss https://hackmd.io/-jpsOWYoRACRNF3G80Hkuw?edit Other teams: T-compiler T-rustdoc Doctests https://github.com/rust-lang/testing-devex-team/issues/5

2025-03-25 eric: Check if anyone is interested in helping with blanket source replacement?https://rust-lang.zulipchat.com/#narrow/channel/246057-t-cargo/topic/Possibility.20to.20replace.20any.20source.20in.20config.2Etoml https://github.com/rust-lang/cargo/issues/11406 jacob: There was some related work on the git/sparse equivalence. There are some landmines here. ed: Doesn't know how it would work with git, so that seems like that needs some work. But seems like there is merit. How do you break out of the proxy, where there is a mix (inclusion/exclusion rules). Could put on them for determining use cases. Reach out on the integration stream to find what requirements clients have. jacob: Nuget (or some other) has something more extreme, where it is substituting networking at a low-level, and you can customize what you want to do. "Here's URL, give me a file." A low-level system could help avoiding missing things in the future. weihang: Why can't implement outside of cargo? An http proxy should be able to handle any request. eric: Will try to follow up with some questions and level set some expectations. epage: review open questions on build.build-dir, see https://github.com/rust-lang/cargo/issues/14125

Workflows Important considerations when asking "what is slow?" What workflows are you having problems with? What workflows are you avoiding because they are slow? X% faster isn't always important but the end-user impact. For example, dropping 1 minute off of a 20 minute CI won't change user behavior. Instead CI time falls into buckets like "instantenous", "get a coffee", "work on something else", "come back the next day".

This is a summary of what has been happening around Cargo development for the last 6 weeks which is approximately the merge window for Rust 1.86. Plugin of the cycle ImplementationPolishing diagnoxtics cargo package dirty check Cargo script Splitting build-dir out of target-dir Design discussions

This is a summary of what has been happening around Cargo development for the last 6 weeks which is approximately the merge window for Rust 1.88. Plugin of the cycle Implementation Design discussions Misc Focus areas without progress Plugin of the cycle Cargo can't be everything to everyone,

This is a summary of what has been happening around Cargo development for the last 6 weeks which is approximately the merge window for Rust 1.85. Plugin of the cycle ImplementationRustflags and caching Report progress in the taskbar cargo publish dirty-check performance Future-proofing the Index Design discussions

2024-12-17 Cancelling next two meetings?agreed, will cancel until jan 7 epage: task bar FCP: https://github.com/rust-lang/cargo/pull/14615#issuecomment-2546346489 term.progress.taskbar = true josh: is there a path where we don't need this in the long-term (to avoid maintaining it)? An environment var opt-out. Thinking about long-term where we might not want a config option.ed: Some people like having the option to turn it off it is something they don't want (visual concerns, unusual compatibility, etc.). epage: switch cargo publish to run a check instead of a build?

This is a summary of what has been happening around Cargo development for the last 6 weeks which is approximately the merge window for Rust 1.87. Plugin of the cycle Implementation Design discussions Misc Focus areas without progress Plugin of the cycle Cargo can't be everything to everyone,

This is a summary of what has been happening around Cargo development for the last 6 weeks which is approximately the merge window for Rust 1.84. Plugin of the cycle ImplementationSimple english in documentation Build Script API Replacing mtimes with checksums Rustflags and caching Snapshot testing JSON schema files

This is a summary of what has been happening around Cargo development for the last 6 weeks which is approximately the merge window for Rust 1.83. Plugin of the cycle ImplementationMSRV-aware Cargo Shell completions Public/private dependencies Optimizing cargo Design discussions

2024-09-24 ed: FCP remindershttps://github.com/rust-lang/cargo/pull/14404 for cargo scriptweihang: Can we scope this under just cargo script usage? ed: can, but not sure why we would since it could complicate things like documentation eric: msrv stabilization ed: local branch ready, still working on documentation, set up in parallel discussions with josh, will wait for last night's MSRV change for people to test that. Still planning this release. josh: Got through 90% discussion at rustconf, very close. weihang: default to lockfile v4

This is a summary of what has been happening around Cargo development for the last 6 weeks which is approximately the merge window for Rust 1.82. Plugin of the cycle Implementationcargo info Shell completions MSRV-aware Cargo cargo publish --workspace cargo::error build script directive cargo update --precise <prerelease> Snapshot testing

MSRV David "support" Jacob:Norms like semver where there is a default and people document otherwise (whether msrv is breaking, features that are unstable, etc) This makes the norms legible to cargo and so people can leverage them What is part of toolchain?Everything versioned with rustup Is rust-analyzer part of the toolchain? It is generally received through other means but can be received through rustup SymptonUsing rust-analyzer out of rustup with their MSRV version but not compatible with editorrust-analyzer hacks in support for a feature until there is a native version in vscode and then its removed

This is a summary of what has been happening around Cargo development for the last 6 weeks which is approximately the merge window for Rust 1.81. Plugin of the cycle ImplementationSnapshot testing Optimizing git sources Duplicate package name warning Removing implicit features Garbage collection Turn all warnings into errors Merging cargo upgrade into cargo update

2024-06-25 out: epage Project Goals for Cargo?Are there projects Cargo wants to put on the roadmap, that potentially need coordinating with other teams, or that people may want to get a visible commitment on before starting to work on (e.g. because they want to get approval from their employer to spend time on them)? weihang: what is the timeframe to submit goals?josh: fuzzily in the next week or two eric: clarifying, can goals just be within a team? josh: yes.

This is a summary of what has been happening around Cargo development for the last 6 weeks which is approximately the merge window for Rust 1.80. Plugin of the cycle Implementationcheck-cfg User-controlled cargo diagnostics -Ztrim-paths MSRV-aware Cargo Removing implicit features Normalizing published manifest files Merging cargo upgrade into cargo update

This is a summary of what has been happening around Cargo development for the last 6 weeks which is approximately the merge window for Rust 1.79. Plugin of the cycle ImplementationDeprecations User-controlled diagnostics MSRV-aware Cargo Edition 2024 Normalizing Published Package Files cargo info