You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(bulk-assets): retry publishing assets whose scan was pending
Assets still being scanned for malware were skipped on every publish run
with only a console warning, leaving no way to publish them once the scan
finished. Record those skips to pending-scan.json in the bulk operation
folder, and add --retry-pending to re-check their status and publish the
ones that came back clean.
The log is self-pruning: a retry drops the entries it published along with
any that turned quarantined, keeping only those still scanning. It is also
excluded from clearLogs(), since a scan can outlast the gap between two
unrelated runs.
Quarantined assets are never retried, and the flag is rejected for
unpublish, delete and move — scan status only gates publish.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
SCAN_STATUS_FETCHING: 'Checking asset scan status for {count} assets...',
233
233
NO_PUBLISHABLE_ASSETS: 'No publishable assets — all assets are either still scanning or quarantined.',
234
+
SCAN_RECHECK_SUMMARY:
235
+
'Re-checked {total} pending asset(s): {clean} now clean (will publish), {pending} still scanning, {quarantined} now quarantined (skipped permanently).',
236
+
NO_PENDING_SCAN_ITEMS_IN_LOG:
237
+
'No pending-scan assets found in {path} — nothing to retry. Assets are recorded there when a publish run skips them for a scan still in progress.',
234
238
};
235
239
236
240
/**
@@ -423,6 +427,8 @@ const flagDescriptions = {
423
427
YES: 'Skips interactive confirmation prompts and runs the command immediately using the provided options. Useful for automation and scripts.',
424
428
RETRY_FAILED:
425
429
'(optional) Use this option to retry publishing the failed entries/assets from the logfile. Specify the name of the logfile that lists failed publish calls. If this option is used, it will override all other flags.',
430
+
RETRY_PENDING:
431
+
'(optional) Re-checks the malware scan status of assets a previous run skipped because scanning was still in progress, and publishes the ones that are now clean. Specify the bulk operation folder used by that run. Quarantined assets are never retried.',
426
432
427
433
// Entry-specific flags
428
434
CONTENT_TYPES: 'Content type UIDs to perform operation on. If not provided, operates on all content types.',
0 commit comments