Tracking Issue for publish-timeout · Issue #11222 · rust-lang/cargo (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

Summary

RFC: N/A
Original issue: #9507
Implementation: #11230, #11062
Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#publish-timeout

Controls the timeout between uploading the crate and being available in the index

Unresolved Issues

• What name makes this clear?
• What should this look like? Is this per-CLI run or across all CLI runs (ie arg vs config)? Is this across all registries or per registry? Should the registry itself have a say when we publish

Future Extensions

No response

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.