[Manager] Fix banned status logic to only check Registry status (#4535)

This commit is contained in:
Jin Yi
2025-07-26 07:14:38 +09:00
committed by GitHub
parent 24ae277ebe
commit 0721cdbd64
2 changed files with 2 additions and 12 deletions

View File

@@ -280,14 +280,7 @@ export function useConflictDetection() {
// Status information
registry_status: undefined, // Node status - not critical for conflict detection
version_status: versionData.status,
is_banned:
versionData.status === 'NodeVersionStatusBanned' || !isEnabled,
ban_reason:
versionData.status === 'NodeVersionStatusBanned'
? 'Version is banned in Registry'
: !isEnabled
? 'Package is disabled locally'
: undefined,
is_banned: versionData.status === 'NodeVersionStatusBanned',
// Metadata
registry_fetch_time: new Date().toISOString(),
@@ -306,8 +299,7 @@ export function useConflictDetection() {
package_name: pack.name || packageId,
installed_version: pack.latest_version?.version || 'unknown',
is_enabled: isEnabled,
is_banned: !isEnabled,
ban_reason: !isEnabled ? 'Package is disabled locally' : undefined,
is_banned: false,
registry_fetch_time: new Date().toISOString(),
has_registry_data: false
}

View File

@@ -89,8 +89,6 @@ export interface NodePackRequirements {
| 'NodeVersionStatusFlagged'
/** @description Whether package is banned (derived from status) */
is_banned: boolean
/** @description Reason for ban if applicable */
ban_reason?: string
// Metadata
/** @description Registry data fetch timestamp */