v2.7.0

New: Go-Live and Expiration columns on the post list

You can now see when each post goes live and when it expires without opening it.

Each schedule has a new "Post List Columns" checkbox in its Add/Edit window. It's off by default, so nothing changes until you turn it on.
When it's on, that post type's list shows a Go-Live Date column and an Expiration Date column in place of the standard Date column.
Both columns can be sorted by clicking the header. Posts with no date are still listed, shown with a "—".
Dates use your site's date format. Schedules that use exact times show the time as well.
If a post type has more than one schedule, the columns follow the first schedule that has the option turned on.

PostyCal 2.6.0

• Settings page redesigned to match the visual style of CDG Core's own settings screen: a sidebar nav in place of the old top tabs, sections in cards, and the same typography, spacing, buttons, and form controls
• The Post Types tab now lists other available post types — every public post type on the site PostyCal didn't create itself (core Post/Page, a type from ACF's Post Type UI, CPT UI, or hand-coded elsewhere) — so it's obvious at a glance what's already usable on the Schedules tab without creating anything
• The settings page now always opens on the Schedules tab, regardless of setup state

PostyCal 2.5.1

• Settings page now opens on the right tab. The tab order was Schedules → Post Types → Taxonomies, backwards from the documented setup order — a first-time user landed on a tab with nothing to select. Tabs are now ordered Post Types → Taxonomies → Schedules, and the page opens on Post Types until at least one schedule exists, after which it opens on Schedules
• The How PostyCal Works box now shows above the tabs on every visit instead of only inside the Schedules tab, and notes that you can skip straight to Schedules if you already have a post type and taxonomy to reuse
• Added a Settings link to PostyCal's row on the Plugins screen
• A managed post type's list screen (Posts, or any custom post type with a schedule) now shows a Scheduled by PostyCal link alongside All / Published / Trash, so there's a way back to the schedule from the content it governs
• The Plugins-screen description now describes what PostyCal actually does, replacing wording left over from before the 2.1 rewrite

PostyCal 2.5.0

• Fixed a fatal error that locked every non-administrator out of wp-admin. add_options_page() returns false for a user without manage_options, and assigning that to a typed property under strict_types threw a TypeError on admin_menu — which fires on every admin screen. Editors, authors, contributors and subscribers got "There has been a critical error on this website" on every page of the dashboard. Present since at least 2.4.0
• Added a Check for updates link to PostyCal's row on the Plugins screen, next to "View details". Core only offers "Check again" on Dashboard → Updates, which re-checks every plugin and theme on the site; this re-checks PostyCal alone and reports the result inline

PostyCal 2.4.1

• Scheduled runs no longer issue a database query per post to read its current term; on a 25,000-post archive a run dropped from roughly 20,100 queries to 620
• Transition passes fetch post IDs and walk them in batches, so memory stays flat instead of loading every matching post at once — the same archive went from about 160 MB to 22 MB, well clear of the memory limit that was killing runs on large sites
• Date-only values now parse at midnight instead of inheriting the current time, so a post going live is stamped with its go-live date at 00:00 rather than whatever time the run happened to fire
• Editor notices describe what PostyCal will actually do when only one date is filled in, replacing the previous claim that a post would not publish until both were set
• A go-live and expiration date on the same day no longer warns, since that is a valid one-day run
• With two schedules on one post type, a problem in the first no longer hides a problem in the second, and each notice names the schedule it refers to

PostyCal 2.4.0

• Added in-dashboard updates: new GitHub Releases are now offered as plugin updates under Dashboard → Updates, rather than needing a manual zip upload
• Declares an Update URI, which also prevents WordPress accepting an update for this plugin from wordpress.org
• Release lookups are cached for 6 hours, and for 15 minutes after a failure; "Check again" bypasses the cache
• Releases without a plugin zip attached, and drafts and pre-releases, are never offered as updates

PostyCal 2.3.1

• The release workflow now also runs when a release is published from the GitHub UI. Tags created that way fire release and create but not push, so a UI-cut release was getting no plugin zip attached
• When the release already exists, the build attaches the zip to it rather than failing, and supplies notes only if the release has none — hand-written notes are never overwritten