Add support for release date

[cyanzhong]

No description provided.

[Copilot]

Pull request overview

Adds registry check-in timestamps for extension and theme releases.

Changes:

• Adds date schemas, stamping, normalization, and tests.
• Updates publishing to stamp dates after merge.
• Backfills dates and initial-release notes across registry entries.

Reviewed changes

Copilot reviewed 41 out of 41 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
.github/workflows/publish.yml	Enables publish-time date stamping.
README.md	Documents release metadata.
scripts/build.mjs	Stamps and propagates dates.
scripts/registry-date.mjs	Implements metadata stamping and normalization.
test/registry-date.test.mjs	Tests date metadata behavior.
schemas/extension.schema.json	Defines extension date format.
schemas/theme.schema.json	Defines theme date format.
schemas/index.schema.json	Adds dates to generated entries.
index.json	Backfills generated latest metadata.
extensions/markedit-ai-writer.json	Adds release date.
extensions/markedit-authorship.json	Adds initial metadata.
extensions/markedit-bidirectional-preview-sync.json	Adds release date.
extensions/markedit-devtools.json	Adds initial metadata.
extensions/markedit-direct-preview.json	Adds initial metadata.
extensions/markedit-enhanced-paste.json	Backfills release metadata.
extensions/markedit-highlight.json	Adds initial metadata.
extensions/markedit-hitl-review.json	Adds initial metadata.
extensions/markedit-language-data.json	Backfills release metadata.
extensions/markedit-mindmap.json	Adds initial metadata.
extensions/markedit-mte.json	Adds initial metadata.
extensions/markedit-native-text-shortcuts.json	Adds release date.
extensions/markedit-outline-sidebar.json	Adds release date.
extensions/markedit-prettier.json	Backfills release metadata.
extensions/markedit-preview.json	Backfills release metadata.
extensions/markedit-proofreading.json	Adds initial metadata.
extensions/markedit-quick-emoji.json	Adds initial metadata.
extensions/markedit-reference-style-links.json	Adds initial metadata.
extensions/markedit-rendered-math.json	Adds initial metadata.
extensions/markedit-theme-zero.json	Backfills release metadata.
extensions/markedit-vim.json	Adds initial metadata.
extensions/markedit-wikilinks.json	Adds initial metadata.
themes/markedit-theme-basic.json	Backfills release metadata.
themes/markedit-theme-catppuccin.json	Backfills release metadata.
themes/markedit-theme-duotone.json	Backfills release metadata.
themes/markedit-theme-gruvbox.json	Backfills release metadata.
themes/markedit-theme-noctis-lilac.json	Backfills release metadata.
themes/markedit-theme-nord.json	Backfills release metadata.
themes/markedit-theme-one-dark.json	Backfills release metadata.
themes/markedit-theme-quietlight.json	Backfills release metadata.
themes/markedit-theme-tokyo-night.json	Backfills release metadata.
themes/markedit-theme-vscode.json	Backfills release metadata.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 46 out of 46 changed files in this pull request and generated no new comments.

Suppressed comments (2)

scripts/assets/index.js:23

• version.dataset.notes is checked using truthiness, which treats an intentionally empty data-notes="" attribute as “missing”. That can make the client-side tooltip differ from the server-rendered one (which treats empty-string notes as present). Check for undefined instead of truthiness so the presence/absence of the attribute controls the formatting consistently.

  document.querySelectorAll('.ver[data-date]').forEach((version) => {
    const formattedVersionDate = formatLocalDate(version.dataset.date, { dateStyle: 'medium' });
    if (formattedVersionDate) {
      version.title = version.dataset.notes
        ? `${formattedVersionDate}: ${version.dataset.notes}`
        : formattedVersionDate;
    }

.github/workflows/publish.yml:24

• The workflow rebases and pushes back to main (git pull --rebase + git push). With the default shallow checkout, this can fail or behave unexpectedly when the remote branch has advanced (e.g., concurrent merges/runs) because the local clone may not have enough history for a clean rebase. Restore an unshallow checkout for reliability of the self-commit step.

      - uses: actions/checkout@v5