Hugh Hackman
3b734dfa69
The release job used pnpm/action-setup@v5 without a version input, which requires a packageManager field in package.json. Repos that don't have this field fail at Setup pnpm, blocking all releases. Mirror the resilient two-step pattern already used in plugin-ci.yaml: - If packageManager is present: use Corepack (respects pinned version) - If absent: fall back to pnpm/action-setup@v5 with version: latest Fixes the systemic v1.0.0 release failures across kube-vip, sealed-secrets, tns-csi, and rook (PRI-866). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>