bazelbuild / bazelbuild/rules_rust

Drop support for non-sparse registries?

Open
#3,568 1 comment 0 reactions 0 assignees View on GitHub
crate-universe needs-triage
Dominant language
Starlark
Stars
843
Forks
651
Avg merge
2d 18h
Merged PRs (30d)
15

Description

Dropping these will significantly reduce the dependency tree for cargo-bazel, making it easier/faster to iterate on it and reducing security surface area.

- Rust has defaulted to sparse for crates.io since 1.68, which shipped March 9, 2023 (over 2 years ago)
- Artifactory has supported the sparse protocol since 7.46.3, and defaulted to on since 7.58 which shipped March 31, 2023

The ecosystem seems to have largely adopted sparse registries given the performance benefit

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.