πŸ“‹ RELEASE NOTES

Release Notes

Version history and changelog for WP Maintenance Manager.

v1.6.10
2026-06-10
Latest

Grid view usability improvements, and a fix for version display in the distributed package

Three usability improvements around the grid view. This release also fixes a bug where the in-app version display stayed at 1.6.8 after installing v1.6.9, caused by an issue in the distribution package build process.

New
  • Each card in the grid view now shows the tags assigned to that site as small chips. They use minimal space and let you see at a glance which tags are attached for filtering.
  • Site lists can now be reordered by drag and drop (both list and grid view). Grab the drag handle (::) and move it; the drop position is shown as a thin line on the relevant edge of the target card, letting you change the default sort order to anything you like.
Improved
  • Each grid card now has Clone and Delete actions, matching the list view. Clone, Delete, and History are shown as compact icon buttons with tooltips on hover.
  • Status badge layout in the site list has been tightened up. Even on narrow cards, the Edit button no longer gets squeezed into vertical text, and badges like "Success / 12 days ago" no longer drift out of alignment.
Fixed
  • Fixed a bug where the in-app version display stayed at 1.6.8 after installing v1.6.9, causing the update prompt not to clear. This was caused by an issue in the distribution package build process. We added full cleanup of build caches before each build, ensured the version information is bundled correctly, and added automatic post-build verification to prevent recurrence. The maintenance features themselves were not affected.
v1.6.9
2026-06-09

DB Backup and Plugin List Stability

A maintenance release addressing two issues: DB backup not completing within the time limit on some sites, and certain plugins causing WP-CLI to fail at runtime.

Fixed
  • The DB backup now passes standard lock-relaxing flags (--single-transaction --quick --skip-lock-tables) to mysqldump by default. On sites with many concurrent updates, this may help backups complete more often.
  • Plugins listed in "Excluded Plugins" are now also skipped at WP-CLI runtime. On environments where a specific plugin causes WP-CLI to fail, this can serve as a workaround to keep maintenance and plugin list retrieval running.
Improved
  • The DB backup now logs progress (changes in the backup file size) while running. If the backup does not complete within the time limit, you can tell whether it was "just slow" or "stuck at some point."
  • When a DB backup fails, the server-side process status and MySQL execution thread state are now captured to the log automatically. If the same symptom appears again, this provides material for diagnosing the cause.
v1.6.8
2026-06-03

Plugin List and Update Detection Stability

A maintenance release that more reliably resolves an issue where, on some hosting environments, fetching the plugin list or detecting available updates could fail due to PHP warning messages emitted by the server.

Fixed
  • On servers combining an older WP-CLI with a newer PHP (8.2 or later), a flood of warnings such as "PHP Deprecated" could cause fetching the plugin list or detecting updates to fail. This is now resolved more reliably.
  • Those warning messages are no longer shown verbatim in bulk on the error screen.
Improved
  • During maintenance, each site's thumbnail and pending-update badge now refresh the moment that site finishes, instead of only after the whole batch. When maintaining many sites at once, you can see progress as it happens.
  • Sites that ended in an error are now highlighted in the site list with a red border and a light red background (completed sites use a green border). It is now much harder to miss an error when maintaining many sites at once.
  • When maintenance finishes, the selection checkboxes for the sites you just ran are cleared automatically. You can still tell which sites were maintained from their green "completed" border (shown for 24 hours).
v1.6.7
2026-06-02

Browser Update Stability and Site List Improvements

A maintenance release improving the stability of browser-based updates and the usability of the site list.

Fixed
  • Fixed an issue where WordPress core updates could stop midway during browser-based updates (without SSH)
  • Fixed an issue where an error could appear during the post-update check in browser-based updates
Improved
  • After editing and saving a site, the list now keeps your scroll position instead of jumping back to the top
  • The pending plugin update badge now refreshes immediately without needing to switch views
v1.6.6
2026-05-29

Better visibility on the site list β€” progress, pending updates, and elapsed days at a glance

v1.6.6 significantly expands the visual information on the site list so you can understand the state of multiple sites without opening them. Currently-running, queued, and completed sites are distinguished by frame colors. The πŸ”Œ plugins button shows a pending update count badge per site. The time since the last maintenance run is shown with a color-coded "N days ago" badge. We also fixed the issue where site selections (maintenance queue checkboxes) would disappear when switching views, and improved the cases where plugin info couldn't be fetched on certain modern PHP environments.

New
  • Maintenance progress is now visualized via frame colors on the site list. The site currently being processed gets a pulsing blue frame, sites queued for maintenance get a dashed light-blue frame, and completed sites get a solid green frame. The "completed" state persists for 24 hours so you can later look back at "which sites were run today"
  • The πŸ”Œ Plugins button on the site list now shows a "pending updates" count badge. After running the cross-site update dashboard, the number of pending plugin updates is displayed as a red badge on the top-right of each site's πŸ”Œ button β€” you can see "how many updates are waiting" without opening anything. Opening the per-site πŸ”Œ plugins modal also refreshes that site's badge. Badge data is retained for 30 days, with a tooltip showing "last fetched: N days ago"
  • "Days since last maintenance" badge added to the site list. Next to the last maintenance date, a relative day count like "15 days ago" or "30 days ago" is shown, color-coded by elapsed time: green for 0–14 days, gray for 15–29, amber for 30–59, red for 60+. Sites that haven't been maintained for a while stand out at a glance
Improved
  • Site list selections (maintenance queue checkboxes) no longer disappear when switching between list / grid view, paging, or changing filters. Previously, picking 10 sites on the list view and then switching to grid view would wipe all checks β€” that's fixed. Selections across multiple pages are also preserved together
  • Added an "N selected Β· Clear all" chip in the toolbar. It always shows how many sites you have selected, and the "Clear all" link clears the selection in one click β€” even if the selection spans multiple pages. The chip is hidden when nothing is selected
  • The "items per page" setting (10 / 25 / 50 / 100) for the site list is now remembered separately for list view and grid view. For example, "50 items per page on list view, 25 on grid view" is now a valid persisted preference. It survives app restarts
  • Site list selections (checkboxes) are now automatically cleared every time the app starts. This prevents the case where checkboxes left over from a previous session caused unintended sites to be maintained. Within the same session, view switches and page changes still preserve selections
Fixed / Improved
  • Improved a case where plugin info fetching could fail on some hosting environments. On servers running PHP 8.2 or later with a slightly older bundled WP-CLI, the WP-CLI internal deprecation warnings could interfere with the plugins modal and the cross-site update dashboard. This release absorbs that warning noise so plugin info can be retrieved reliably. This addresses the gap where SSH and WP-CLI path tests both passed but plugin info still wouldn't load
  • Updated the user guide, FAQ, and chatbot knowledge to match the new site list UI (badges, frame colors, selection chip)
v1.6.5
2026-05-25

SSH connection stability improvements β€” maintenance release

v1.6.5 is a maintenance release focused on shoring up the SSH connection path. For users who manage multiple SSH keys in ~/.ssh/ (typical for freelancers and agencies with separate keys per client), repeated connection tests and maintenance runs could in some cases trigger the hosting provider's protective mechanism that temporarily blocks the source IP after a burst of authentication failures. We've adjusted the app behavior to avoid that. We've also removed a related warning about private-key file permissions that was not actually needed in this app's context.

Fixed / Improved
  • Reduced the risk of being temporarily blocked by the hosting provider when repeating connection tests or maintenance runs in multi-key environments. If you manage multiple SSH keys (one per server, multiple keys loaded into your SSH agent, etc.), a single connection could end up offering several keys before reaching the intended one, hitting the provider's burst-of-failures protection (the rule that temporarily refuses the source IP after a short flurry of authentication failures). This release tightens the app so it only tries the key you specified in the site settings, leaving other keys in your environment alone
  • Removed the "private key file permissions are too open" warning and its fix button shown before connection tests. The app uses the paramiko library internally, which (unlike the OpenSSH command-line client) does not enforce StrictModes on the key file, so 644 permissions do not actually prevent the connection from working. The warning was kept as a precaution for OpenSSH command-line users, but in some environments it was triggering misleading follow-up steps, so we've removed it in this release. Tightening private key permissions to 600 manually is still recommended in general β€” see the SSH troubleshooting section of the User Guide if you want to do it by hand
v1.6.4
2026-05-21

Site edit modal cleanup & small fixes β€” usability release

v1.6.4 reorganizes the site edit modal into a 3-tab layout (General / SSH / WordPress) and adds a free-form notes field. Alongside, it fixes the issue where Core / PHP version badges could disappear after editing a site, makes the "SSH profile required vs. browser-only" choice explicit when saving, and brings a few small i18n improvements that were still falling back to English in the Japanese UI.

New
  • Site Add/Edit modal is now organized into 3 tabs β€” πŸ“‹ General (site name, category, tags, notes, optional toggles) / πŸ–₯ SSH (SSH profile, WordPress install path, WP-CLI path) / πŸ”΅ WordPress (admin URL / user, Basic auth, excluded plugins). Tab content stays in sync when switching, and if a required field on a different tab is empty when you press Save, the app auto-switches to that tab and shows the validation tooltip on the field
  • Added a πŸ“ Notes field (optional, up to 5,000 characters) on the General tab. Use it for site-specific context that doesn't fit other fields β€” contract renewal month, hosting provider support contact, client point-of-contact, operational caveats. Does not affect maintenance execution
Fixed / Improved
  • Fixed an issue where changing just the category or tag of a site (without touching anything else) would drop the Core / PHP version badges previously fetched by maintenance runs. Backend-managed metadata (core_version, web_php_version, version source) is now properly preserved when the front-end saves an edit
  • Improved the "no-op Save button" case on the Site Add/Edit modal β€” when neither an SSH profile was selected nor "Don't use SSH" was checked, the Save button silently did nothing (validation was failing invisibly). The two choices are now explicit and mutually required, and if both are empty the app auto-switches to the SSH tab and shows a tooltip on the empty field
  • Fixed an issue where, right after clicking an auto-detected path chip to fill the WordPress install path, pressing Save could still report the field as empty even though the value was visible in the input. The chip-click now properly fires input/change events so HTML5 validation sees the new value
  • The cross-site plugin updates dashboard error messages now localize properly β€” Japanese UI shows "WP-CLI エラー: ..." / "SSH 鍡エラー: ..." instead of "WP-CLI error: ..." that previously slipped through
  • Settings Backup modal: the individual backup buttons (Notification Settings / SSH Profiles) used to stay in Japanese even when the UI was in English. They now switch correctly to "Notification Settings" / "SSH Profiles" on the English UI
  • Updated the LP user guide, FAQ, and chatbot knowledge to match the new 3-tab site edit modal. Questions like "which tab has the WP-CLI override field?" now have clear answers
v1.6.3
2026-05-20

SSH connection & private-key stability β€” maintenance release

v1.6.3 is a maintenance release that broadly shores up the SSH-setup pain points. Private keys issued by some hosting providers (PKCS#8 plain/encrypted, PuTTY format, etc.) can now be read directly without pre-conversion. We also added automatic SSH-key permission diagnosis & fix, improved WordPress install-path auto-detection, and stabilized the browser supplemental update flow β€” modest but practical improvements bundled together.

New
  • Added automatic SSH-key permission diagnosis & fix. The "UNPROTECTED PRIVATE KEY" / "Permissions are too open" failures (caused by overly-permissive private-key file permissions) are now detected on the connection-test screen. Clicking "πŸ”§ Fix and continue" applies chmod 600 on Mac/Linux or the icacls equivalent (current-user-only full control, inheritance disabled) on Windows. Only file attributes on your computer are changed β€” the key contents and the server itself are untouched
  • Improved error messages for unsupported key formats (SSH.com commercial format, corrupted files, accidentally specifying a public key, etc.). When detected, the message now includes actionable next steps such as "convert it to OpenSSH format"
Fixed / Improved
  • Improved compatibility with private keys issued by some hosting providers. In addition to the previously supported OpenSSH, PKCS#1 (RSA), and SEC1 (EC) formats, the app now accepts PKCS#8 plain text, PKCS#8 encrypted, legacy PEM encrypted (Proc-Type: 4,ENCRYPTED), and PuTTY format (.ppk v2 / v3) private keys directly. Prior openssl or PuTTYgen conversion is generally no longer required (SSH.com commercial format and legacy DSA keys remain unsupported; in those cases an actionable error message is shown)
  • Fixed an issue where the browser supplemental update (which updates premium plugins with their own update servers via the WP admin) was incorrectly reporting "admin login failed" when WordPress showed the periodic "Is this still your email address?" verification screen. The app now automatically clicks "Yes, this email is correct" and continues the update flow
  • Improved PHP version badge coverage in the site list β€” some sites were not showing a badge due to hosting layout differences. The badge is now reliably populated via the WordPress site URL with a WP-CLI fallback. Values fetched via WP-CLI are shown with an amber badge + trailing asterisk so you can tell at a glance that they are a best-effort reference (CLI side may differ from web-facing PHP)
  • Fixed WordPress install-path auto-detection failing on hosting providers that use specific login shells (csh, etc.). For SSH profiles that are already configured, the auto-detect button now lists every WordPress install on the server in the dropdown
  • Improved the major-rental-server SSH port and private-key permission information across the LP and in-app help (Xserver = 10022 / Sakura Internet = 22 / ConoHa WING = 8022, etc.) so the correct values are easier to confirm when SSH setup gets stuck
v1.6.2
2026-05-17

Cross-site dashboard Γ— Selected Plugin Update Γ— major site list improvements β€” managing many sites just got easier

This release tackles real-world agency requests: "update one specific plugin across many sites quickly" and "see the status of each site at a glance." A cross-site plugin updates dashboard, scope-narrowed safe updates, support for HTTP basic-auth-protected sites, and richer site list information are the headline additions. A root-cause fix for missed paid-plugin updates is also included.

New
  • Added the Cross-Site Plugin Updates Dashboard. Open it via the "Plugin Updates" button in the toolbar to see every "plugin update available" across all your sites in a single view. Entries are grouped by plugin name, e.g. "Elementor: 3 sites need updating (4.0.0 β†’ 4.0.8)", so it's instantly clear which plugin is outdated and where. The parallel SSH scan finishes quickly even with many sites, with prominent progress bar / completed count / current site name / ETA. Results are cached in the browser for 24 hours and shown instantly on the next launch
  • Added Selected Plugin Update. In the dashboard, tick the (site Γ— plugin) checkboxes and click "Update Selected Plugins" to update only the chosen plugins. The run executes exactly like a regular maintenance β€” DB backup, per-plugin HTTP check, automatic pinpoint rollback on failure, post-update visual verification, summary email β€” except that core, themes, and translations are skipped. Unlike other tools' "Update All" buttons, this keeps the full safety net while narrowing the scope. The log history and report are tagged with "Selected Update" and the target plugin names
  • Added a πŸ”Œ Plugin List modal to each site card. Click it to see every plugin installed on that site, with tabs to switch between "All" and "Update available" (read-only). Only shown for sites with SSH configured
  • Added a πŸ›  Admin Panel Link to each site card. Clicking it opens the WordPress admin in a new tab (manual sign-in). Handy when you frequently jump between sites and their admin panels
  • Added Site thumbnails + Grid / List view toggle. After each maintenance run, a thumbnail is generated automatically from the home page screenshot and shown on each site card. A toolbar button switches between a thumbnail-rich grid view and a vertical list view
  • Added Core / PHP version badges + multi-select filters. Each site shows a WordPress core version badge (e.g. Core 6.9) and a web-side PHP version badge (e.g. PHP 8.3). The toolbar lets you filter by multiple exact versions β€” useful for inventory tasks like "How many sites are still on PHP 7.4?"
  • Added HTTP Basic authentication support for protected sites. A collapsible "πŸ” Basic auth" section on the site edit screen accepts a username and password (encrypted on disk). Visual checks, thumbnail capture, and browser residual update now work on basic-auth-protected staging / dev environments
  • Renaming a site no longer loses its thumbnail, before/after screenshots, or DB backup history. Previously, when you renamed a site, the existing thumbnail, screenshots, and DB backups were orphaned β€” treated as belonging to a different, old site β€” and would visually appear to have been reset. From now on, all files follow the site through any rename (tracked by a stable internal ID). Feel free to fix client-name typos or rename a site when moving from staging to production. On first launch after the update, existing thumbnail / screenshot / backup folders are automatically migrated to the new format (one-time, idempotent β€” the existing "last 3 backups retained" rotation continues unchanged)
Improved
  • Fixed an issue where plugins and themes with their own custom update mechanisms could be missed on certain server environments. Plugins and themes that appear in the WordPress admin's update list are now more reliably included in automatic updates. Verified on Xserver, ConoHa WING, and Heteml among others
  • Improved the safety mechanism during rollback. By excluding only the plugin that caused the issue, the rollback completes safely while leaving other plugins' update notification filters active
  • The post-update residual check (which verifies that no updates remain pending) now also correctly detects plugins and themes with custom update mechanisms
  • Reorganized the site list action icons into two groups β€” "jump to site" (URL link, πŸ›  admin panel, πŸ”Œ plugins list) and "record actions" (Edit, πŸ•’ log history). The new layout follows the natural reading flow
  • The cross-site dashboard's in-progress scan now continues across modal switches instead of restarting from zero
Fixed
  • Fixed a bug where Selected Plugin Update was not respected by the post-SSH browser residual update, causing plugins outside the selection to be updated. Selected runs now strictly update only the chosen plugins
  • Fixed a bug where a successful Selected Plugin Update would still send a "Updates remaining" warning email about non-selected plugins. Now, successful selected runs send a normal completion email; warnings are only sent when a selected plugin actually fails to update
v1.6.1
2026-05-12

Run sites with mixed PHP versions on a single SSH profile

When sites on the same server use different PHP versions (e.g. server default is PHP 8.2 but one site needs PHP 8.3), you no longer need to duplicate SSH profiles. WP-CLI paths can now be overridden on a per-site basis. Detection of "missed" plugin updates from custom-update-mechanism plugins (ACF Pro, etc.) has also been strengthened.

New
  • Added a "WP-CLI Path (optional override)" field on the site edit screen. The SSH profile's WP-CLI path remains the server-wide default, but you can now specify a different PHP version (e.g. /opt/php-8.3/bin/php /usr/bin/wp) on a per-site basis. Leave blank to use the profile value. No more profile duplication, and SSH key updates only need to be done in one place
  • Sites with an active per-site override are tagged with a "βš™ override" badge in the site list. Hover to see the actual WP-CLI path being used
  • Added a new "Browser Residual Update" feature: after SSH (WP-CLI) updates complete, any plugins still showing "update available" in the WordPress admin (paid plugins like ACF Pro / Yoast SEO Premium / WP Rocket / Elementor Pro that use the standard update mechanism) are processed in one batch via browser automation. Toggle on/off via the "🌐 Browser Residual Update" switch on the site edit screen (default ON). ⚠ Plugins updated via this fallback are NOT eligible for pinpoint rollback (they go through bulk update); this is clearly indicated in execution logs and report emails
Improved
  • The app now force-refreshes WordPress's internal update cache (Transient API, valid up to 12 hours) at the start of each maintenance run. This reduces cases where freshly released plugin versions are missed because of stale cache. The range of updates that can be picked up in a single run is now wider
  • The execution log can now be displayed as a collapsible block at the top of the screen. Even with many registered sites, you no longer need to scroll all the way down to see the log. The block auto-expands when you press the run button, and the header status badge (Idle / Running / Completed Xm Ys / Error) shows progress at a glance. Click to collapse after completion
  • Consolidated description text inside each setting box on the site edit screen ("Browser Residual Update" and "Aggressive Auto-Fix Mode"). It is now visually clear which description belongs to which setting
v1.6.0
2026-05-09

Resolve WP-CLI connection problems in one screen

When the connection test reports "WP-CLI not found," you can now see exactly what's happening β€” and fix it β€” in a single screen. New read-only diagnostic + automatic installation features cover the full troubleshooting flow.

New
  • New "πŸ” Diagnose" button in the SSH profile editor (next to the Test Connection button). It connects to your server in read-only mode and observes the OS, where php lives, the home directory, whether WP-CLI exists and runs, GitHub reachability, and more β€” then proposes a suggested WP-CLI Path as a best-effort reference. Even on hosts where php is not in PATH (e.g. Heteml), it auto-detects versioned PHP aliases like php8.3 and assembles the right command form
  • The diagnostic always shows a clear notice that this is a reference suggestion, not a guarantee. Host-specific quirks may make the suggestion inaccurate, so always verify with the connection test before saving
  • Empirically tested on Xserver, Sakura Internet, ConoHa WING, and Heteml. The same patterns are likely to work on most major hosts (SiteGround, Bluehost, DreamHost, Hostinger, etc.) but this hasn't been formally validated
  • When the diagnostic finds "WP-CLI missing AND home is writable AND GitHub reachable," a new "πŸ“¦ Install WP-CLI automatically" section appears, letting you install WP-CLI to the server with a single click
  • Two-stage installation for safety: first "πŸ§ͺ Test in an isolated path first" places WP-CLI at ~/wpmm_install_test_<timestamp>/wp (your existing ~/bin/wp is untouched). Once verified, "πŸ“¦ Install to ~/bin/wp" performs the production install after a confirmation dialog. Any pre-existing wp is preserved as wp.broken_backup_<timestamp> (the latest 3 backups are kept)
  • The install pipeline guarantees no broken state: download to a tmp file β†’ size check β†’ --info verification β†’ atomic rename only on success. Any failure rolls back automatically. Every SSH command, stdout, stderr, and exit code is saved to logs/install_wpcli_<timestamp>.json for inspection
Improved
  • The connection test now shows the server's stderr response when WP-CLI cannot be started. Common errors like "broken signature," "php: command not found," and "permission denied" are analyzed and presented with a specific actionable hint (the previous version discarded the stderr, which made some failures opaque)
  • Fixed an issue where the SSH profile editor modal could not scroll vertically when its content exceeded the viewport (other modals β€” Categories, Tags, License, etc. β€” were patched as well)
  • Updated the User Guide, FAQ, and chatbot knowledge to recommend the correct fix path (SSH + curl one-liner) when ConoHa WING reports "WP-CLI not found." Uploading via web file manager has been removed from the recommended steps because it can corrupt the PHAR signature
v1.5.8
2026-05-03

Organize sites with categories and tags + per-site log history

Sort registered sites by client or project, filter with cross-cutting tags, and jump straight from each row to its own maintenance log history. Stay organized as your fleet grows.

New
  • Assign a Category (one per site, with a custom color) and Tags (multiple per site) to each registered site
  • New "Categories & Tags" panel under βš™ Settings β€” pick colors with a color picker, edit and delete in bulk
  • New filter dropdowns above the site list for Category and Tags, usable in combination with the text search
  • Tag filter supports both "any of the selected tags" (OR) and "all of the selected tags" (AND) modes
  • When deleting a category, choose to either reset its sites to "Unassigned" or move them to another category in bulk (the impact count is shown up front)
  • Category and tag definitions are included in the settings backup, so they transfer to other machines automatically
  • Each row in the registered-site list now has a "πŸ•’ Logs β€Ί" link that opens the log dialog scoped to just that site
  • Sites now carry a stable internal identifier so log history follows them across renames (existing sites are migrated automatically on first launch β€” no action needed)
  • Flexible log deletion: "Delete filtered results" when status/period filters are active, "Delete this site's logs" from the per-site view, or "πŸ—‘οΈ Delete Selected" for individual rows via checkboxes. A confirmation dialog always shows the exact entry count to prevent accidental "delete all" actions
v1.5.7
2026-04-26

Pinpoint Rollback Hardening and Report Improvements

Strengthened the safety net during maintenance and improved the accuracy and clarity of maintenance reports.

New Feature
  • Warning when attempting to register the same WordPress site twice
Fixed
  • Hardened pinpoint rollback to work reliably even when an update causes a fatal error (WP-CLI safe mode applied to all commands)
  • Pinpoint rollback now also fires when an update causes the site to drop from healthy to a 4xx state (404 / 403 / 401)
  • Maintenance reports now correctly reflect when pinpoint rollback occurred
  • Maintenance report verification summary now shows a warning when rollback could not be completed
  • Improved awkward "HTTP 0" wording in reports to a more readable description
  • Fixed an issue where the WordPress core version displayed in the report was outdated after an update
  • Fixed an issue where database backups were not being saved to your PC during maintenance
  • Updated the description for "Aggressive Auto-Fix Mode" in the Add Site screen to match current behavior
v1.5.6
2026-04-21

Report Improvements and Operational Stability

Made maintenance reports clearer and strengthened internal stability so the app stays reliable for long-term, large-scale operations. Both the Windows and macOS app icons have also been refreshed.

New Feature
  • Updated the Japanese product name to "WP γƒ‘γƒ³γƒ†γƒŠγƒ³γ‚ΉγƒžγƒγƒΌγ‚Έγƒ£γƒΌ" to better align with the English name "WP Maintenance Manager"
Improved
  • Refreshed both the Windows and macOS app icons. Unified them around a black squircle (Apple-style rounded shape, superellipse n=5) with the WP + wrench logo scaled up and centered, so the app no longer looks visually smaller than neighboring icons in the taskbar, Start menu, Dock, or Finder
  • Enriched the inspection summary in reports for sites without SSH. Previously only a single line ("HTTP Status 200 OK") was shown; now six inspection items are displayed as evidence: "WordPress Core", "Admin Login", "Plugins", "Themes", "Translations", and "HTTP Status". Translation updates are also applied automatically via the browser
  • Improved the visual-diff report after maintenance. Previously, a 10% and an 80% diff rate were both reported with the same "minor visual change β€” no issues" wording. Now the message changes across four tiers (minor / moderate / large / significant) based on diff rate, with stronger recommendations for visual verification on larger diffs
  • HTTP status codes now display alongside Japanese labels. Numeric-only notations such as "HTTP 200" or "HTTP 301" scattered across reports and the admin UI are now shown with labels like "200 OK (ζ­£εΈΈ)", "301 Moved Permanently (γƒͺγƒ€γ‚€γƒ¬γ‚―γƒˆ)", and "500 Internal Server Error (ァーバーエラー)", so non-technical users can understand them at a glance
  • Strengthened stability for large-scale operations. Internal write operations have been hardened so rare timing issues are less likely to occur even with many users (β‘ backup downloads are now received under a temporary name and atomically promoted to the final name, preserving the previous backup when the connection drops; β‘‘stale temporary files are cleaned up automatically at app startup; β‘’concurrent writes to configuration files are safely serialized; β‘£when the maintenance log grows large, older months are automatically archived so the history tab stays responsive)
Fixed
  • Fixed an issue where a single plugin update failure could halt the entire run. Timeouts or connection errors on one plugin no longer stop updates of the remaining plugins, themes, and translations
  • Prevented cascading misjudgments after a rollback. Fixed an issue where, after reverting a broken plugin, the next unrelated plugin could be incorrectly identified as the "culprit" and rolled back
  • Reduced unnecessary rollbacks caused by transient network errors. Suppressed misjudgments triggered by momentary network fluctuations
  • Fixed an issue where incomplete backup files could remain on the server when the network dropped during maintenance. Incomplete files are now cleaned up automatically on disconnect
  • Fixed an issue where the WordPress core version was shown incorrectly in reports for sites without SSH. Addresses a bug where a plugin version like "v1.7.11" was sometimes displayed in the WordPress core version field on certain sites
v1.5.5
2026-04-09

Report & Site Management Improvements

Improved report visibility and site management screen usability.

Improved
  • Added an "Inspection Summary" section to white-label reports. Key metrics such as update counts and backup results are now visible at a glance
  • Added a "Fetch from Server" button to the "Excluded Plugins" field in the site editor. You can now select plugins to exclude directly from a list retrieved from the server
  • Reworked SSH profile management so profiles can be shared across multiple sites. Updating a profile now automatically reflects across all associated sites
Fixed
  • Fixed an issue where selecting an SSH profile when adding a site was sometimes not applied correctly
v1.5.4
2026-04-08

New Features Β· UI Improvements Β· Bug Fixes

Added connection and email test buttons to make verifying your settings easy before running maintenance. Also includes platform-specific bug fixes for Windows and Mac.

New
  • Added a "Test Connection" button to SSH profiles so you can verify server settings before adding a site
  • Added a "Send Test Email" button to notification settings so you can confirm your SMTP configuration in advance
Improved
  • Reorganized the site add/edit form β€” WP-CLI path is now visible and the WordPress installation path is displayed more clearly
  • The Exit button is now always visible in the header toolbar
Fixed
  • [Windows] Fixed an issue where antivirus software falsely flagged maintenance as malicious, causing it to be force-stopped mid-run and the app to crash
  • [Windows] Fixed an issue where a Command Prompt window remained open on launch
  • [Mac] Fixed an issue where the app could not be restarted after closing the browser tab
  • [Windows / Mac] Fixed an issue where restoring a settings backup on a different PC caused email notifications and maintenance to stop working
v1.5.3
2026-04-05

UX Improvements Β· Bug Fixes

Backup restore now uses a two-step confirmation flow to prevent accidental restores. An app exit button has been added, and a double-launch bug on browser restart has been fixed.

New
  • Added an app exit button for a clean, safe shutdown
Improved
  • Backup restore is now a two-step flow (select β†’ confirm β†’ execute), reducing the risk of accidental restores
  • Adjusted the rollback flow triggered when an HTTP error is detected after an update
Fixed
  • Fixed an issue where closing the browser and restarting the app could result in a double-launch state
v1.5.2
2026-04-03

Multilingual Terms of Service Screen

The Terms of Service agreement screen shown on first launch now supports switching between Japanese and English. Your selected language carries over to the rest of the app.

New
  • Added a Japanese / English toggle to the Terms of Service agreement screen
  • The language selected on the ToS screen is now applied as the app-wide display language
v1.5.1
2026-04-02

Bug Fixes Β· Multi-Language WordPress Support

Fixed issues with browser-based login and report screenshot matching. Improved compatibility with WordPress sites running in any language.

Fixed
  • Fixed an issue where the admin email verification screen caused login to be incorrectly reported as failed
  • Fixed report screenshots showing images from a different site when site names share a common prefix
Improved
  • Admin panel detection now works reliably on WordPress sites in any language (not just Japanese)
  • Email notification classification is now language-independent for consistent behavior
v1.5.0
2026-04-01

Plan Revision Β· USD Payments Β· BIZ 2-PC Support

Plan pricing and site limits have been revised. USD payment is now supported. The BIZ plan now allows the same license to be used on up to 2 PCs.

New
  • USD payment is now supported. Toggle between Β₯JPY and $USD on the pricing page
  • The BIZ plan now supports registering the same license on up to 2 PCs
Changed
  • LITE plan site limit increased from 10 to 15 sites
  • STANDARD plan price reduced from Β₯8,000 to Β₯4,200 / $28, site limit increased from 50 to 100 sites
  • BIZ plan price reduced from Β₯14,000 to Β₯6,900 / $46, site limit increased from 100 to 200 sites
v1.4.0
2026-03-30

English UI Support

The app's display language can now be switched between Japanese and English.

New
  • The entire UI, logs, and email notifications can now be displayed in English
  • The language toggle button has been moved next to the Run Maintenance button
v1.3.0
2026-03-29

Website Performance & App Icon

Improved website loading speed and added an original app icon.

New
  • The app now displays a custom original icon
  • Privacy Policy page added to the website
Improved
  • Improved loading speed across the entire website
  • Navigation is now consistent across all website pages
v1.2.1
2026-03-18

Payments, Windows Support & Stability

Added credit card payments and significantly improved Windows stability.

New
  • Plan subscriptions can now be purchased and auto-renewed by credit card
  • Auto-update feature added β€” when a new version is released, it can be downloaded automatically
  • "Deregister PC" feature added, allowing license transfers to a new computer
  • Windows installer added
Improved
  • Plugins are now updated one by one; only the problem item is automatically rolled back
  • A notification is now shown when some updates could not be completed
  • Email subject lines now clearly show whether the result is Success, Warning, or Error at a glance
Fixed
  • Fixed an issue where license authentication could fail on Windows
  • Fixed an issue where license information was not properly reset after deregistering a PC
  • Fixed an issue where update checks timed out on some sites
v1.1.0
2025-12-01

Auto-Recovery, License Management & Web UI

Added automatic recovery when a site encounters an error after an update.

New
  • "Auto-recovery" feature added β€” if a site encounters an error after an update, the app automatically rolls back to the previous state
  • Browser-based web UI added for easy site add, edit, and delete operations
  • License management added with per-plan site count limits
  • Screenshot comparison feature added β€” automatically captures and compares screenshots before and after updates to detect visual anomalies
  • DB backups are now automatically saved and the latest 3 generations are retained
Fixed
  • Fixed an issue where SSH connections could become unstable
  • Improved the accuracy of admin panel login detection
v1.0.0
2025-09-01
Initial Release

Initial Release

First release of the desktop app for automated batch updates across multiple WordPress sites.

Initial Features
  • One-click batch updates for WordPress core, plugins, themes, and translations
  • Browser-based auto-update mode available even without SSH access
  • Automatic database backup before each update
  • Email notification of update results after completion
  • Supports major shared hosting providers (Xserver, Sakura Internet, Heteml, ConoHa, etc.)