feat: let a date node pick a time

[lero62]

A date node held a time already — its value is an ISO string — but there was no way to set one.
Payload's DatePicker defaults to the default appearance, and that appearance does not merely hide
the clock: onChange rewrites whatever was picked to noon local time. So the time was not missing
from the form, it was being thrown away on every pick.

time: true on a date node switches the picker to dayAndTime, which leaves the chosen time alone.
It is an ordinary optional parameter, beside min/max on a number and minRows/maxRows on a
list: registered in KEYS as a boolean that only a date may carry, so Code cannot put it anywhere
else, and offered in the builder's settings as Pick a time as well. The default value picker in
those same settings follows the switch, so what an admin sets as the default is what an editor sees.

Left opt-in rather than made the default on purpose. Noon is a safe place for a day-only date: it
survives a render in any timezone without sliding to the previous or next day, and every date node
that exists today was written that way. Turning the clock on for all of them would put midnight
within reach of a careless click and move dates across the date line for the sites that format them
locally.

Nothing changes for a node without the key: same appearance, same noon, same stored shape. The site
is untouched either way — flatten hands a date over as the ISO string it always was.

Checked by hand: the parameter passes validation on a date, is refused on a text node ("time is only
for date") and refused when it is not a boolean; a date without it behaves exactly as before.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
ideal-cms	Ready	Preview	Oct 7, 2026 5:24pm UTC

[github-actions]

🎉 This PR is included in version 1.4.0 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀