Skip to content

Conversation

@epage
Copy link
Contributor

@epage epage commented Dec 10, 2025

What does this PR try to resolve?

Unblocks #15973, #5221

Closes #15491
Closes #16270

How to test and review this PR?

@epage epage added the T-cargo Team: Cargo label Dec 10, 2025
@rustbot rustbot added A-documenting-cargo-itself Area: Cargo's documentation S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Dec 10, 2025
@rustbot
Copy link
Collaborator

rustbot commented Dec 10, 2025

r? @weihanglo

rustbot has assigned @weihanglo.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer


## pubtime

The `pubtime` index field has been stabilized in Rust 1.94.0.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have this set for 1.94

@epage
Copy link
Contributor Author

epage commented Dec 10, 2025

@rfcbot fcp merge T-cargo

@rust-rfcbot
Copy link
Collaborator

rust-rfcbot commented Dec 10, 2025

Team member @epage has proposed to merge this. The next step is review by the rest of the tagged team members:

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.

@rust-rfcbot rust-rfcbot added proposed-final-comment-period An FCP proposal has started, but not yet signed off. disposition-merge FCP with intent to merge labels Dec 10, 2025
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge is blocked on T-crates.io informing us that they have made a decision

@epage epage mentioned this pull request Dec 10, 2025
3 tasks
"rust_version": "1.60",
// The publish time for the package (optional).
//
// In ISO8601 with UTC timezone (e.g. 2025-11-12T19:30:12Z)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we make the description a bit more unambiguous enough for custom registry to implement?

Perhaps follows what we put in cargo generate-lockfile "yyyy-mm-ddThh:mm:ssZ".

Suggested change
// In ISO8601 with UTC timezone (e.g. 2025-11-12T19:30:12Z)
// In ISO8601 with UTC timezone (yyyy-mm-ddThh:mm:ssZ).
// Fractional seconds and offsets are not allowed.
//
// Example: 2025-11-12T19:30:12Z

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It now enumerates the subset of ISO8601

Copy link
Member

@0xPoe 0xPoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rustbot

This comment has been minimized.

@rustbot
Copy link
Collaborator

rustbot commented Dec 12, 2025

This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-documenting-cargo-itself Area: Cargo's documentation disposition-merge FCP with intent to merge proposed-final-comment-period An FCP proposal has started, but not yet signed off. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-cargo Team: Cargo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tracking Issue for _pubtime_ registry-index: Add release date to Index Format

5 participants