You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Activity
tangrufus commentedon Aug 13, 2026
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: