Skip to content

Use real release date for "time" value #122

Open

Description

@coreyworrell

Summary

Hi, it looks like the "time" field in package JSON is the same across all versions of a plugin at the moment and not directly tied to the actual release date of the version. If Composer does add a minimum release age (cooldown) feature (composer/composer#12633) in near future, I assume this is what would be used for that to function? I realize this is just a possibility, but wanted to mention it in case it may be simple to add.

Additional context

No response

Activity

  1. tangrufus commented on Aug 13, 2026

    @tangrufus
    Member

    Cooldown is cool.

    Which timestamp should we use in case stable versions got re-tagged?
    To a greater extent, what is our take on version metadata immutability?

    See:

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions