| 开发者 | shahrear17 |
|---|---|
| 更新时间 | 2026年9月30日 19:38 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
readme.txt at your latest GitHub Release. Each version gets its exact release date, and unreleased work in your repository never shows early. Private repositories work too, with a read-only token stored encrypted.* Fixed - …, Added: …, sub-headings like "Bugfixes", "Release date:" lines and dates in most formats. That covers changelogs written in the styles of popular plugins such as WooCommerce and Yoast SEO.readme.txt at your latest GitHub Release, with exact release dates. Works with public repositories and, with a read-only token, private ones.* Fixed - …, Added: …, sub-headings like "Bugfixes", release-date lines, and dates in most formats.[releasery] shortcode for the classic editor, Elementor and other builders.[releasery] (all products)
[releasery product="my-plugin"] (one product)
[releasery product="my-plugin,my-plugin-pro" per_page="15"]
Every hour by default. You can change this under Releasery → Settings, or click "Check now" at any time. For GitHub, you can also add a webhook for instant updates (shown on the source's edit screen).
WordPress.org does not publish per-version dates. Releasery dates the current version with its "last updated" date and every new version with the day it appears. Older versions keep no date unless your changelog writes one (for example = 1.2.0 - 14/09/2026 =). You can also set a date by editing the entry.
Yes. Create a fine-grained personal access token limited to that repository with read-only "Contents" access and paste it into the source. It is stored encrypted and never shown again.
Not if you tick "Keep my edits" in the entry's Release box. Trashed entries are never re-created, and a published entry is never switched back to draft.
No. Checks run in the background on a schedule; visitors only see the stored entries. The stylesheet is loaded only on pages that show a changelog.
[releasery] shortcode.