After auto-upgrade to 0.13.0 (build 940), hubspot objects list --type contacts fails on a standard-tier portal with:
Missing required scopes: crm.objects.contacts.highly_sensitive.read.v2, crm.objects.contacts.sensitive.read.v2, crm.objects.contacts.read, crm.schemas.contacts.read
The .v2 sensitive scopes are Enterprise-only and cannot be granted on this portal, so re-auth cannot fix it. Additionally, the OAuth consent flow (user-level token) now grants only a minimal scope set (8 scopes vs ~65 on 0.11.0), dropping basic scopes like crm.objects.contacts.read.
Expected: sensitive scopes should be optional/conditionally required, and basic CRM object commands should work on standard-tier portals.
Workaround attempted: no pinned older binaries available via install.sh (versioned URLs 404), and HUBSPOT_NO_AUTO_UPGRADE only prevents future upgrades.
After auto-upgrade to 0.13.0 (build 940),
hubspot objects list --type contactsfails on a standard-tier portal with:Missing required scopes: crm.objects.contacts.highly_sensitive.read.v2, crm.objects.contacts.sensitive.read.v2, crm.objects.contacts.read, crm.schemas.contacts.read
The .v2 sensitive scopes are Enterprise-only and cannot be granted on this portal, so re-auth cannot fix it. Additionally, the OAuth consent flow (user-level token) now grants only a minimal scope set (8 scopes vs ~65 on 0.11.0), dropping basic scopes like crm.objects.contacts.read.
Expected: sensitive scopes should be optional/conditionally required, and basic CRM object commands should work on standard-tier portals.
Workaround attempted: no pinned older binaries available via install.sh (versioned URLs 404), and HUBSPOT_NO_AUTO_UPGRADE only prevents future upgrades.