Summary

Original issue: #5221
Implementation:

• feat(generate-lockfile): Add unstable --publish-time flag  #16265
  Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#lockfile-publish-time
• Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#lockfile-publish-time

Disallow locking to registry packages newer than a specific time

Unresolved Issues

• How do we compensate for the caveats, with one option being to leave this perma-unstable?
• Should we offer a convenient way of getting a compatible timestamp?
• Stabilization of pubtime (Tracking Issue for _pubtime_ #16270)
• evaluate what all formats --publish-time should support (e.g. local time, Z, time zones)
• what format should the Locking message use and its relationship to --publish-times accepted format

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.