Skip to content

Conversation

@camden11
Copy link
Contributor

@camden11 camden11 commented Apr 23, 2025

Description and Context

Previously, converting a developer account to a combined account meant losing the ability to run hs project dev on legacy public apps. This is because a combined account is technically a standard account, which hs project dev didn't support for public apps. This updates the logic in the legacy dev flow to allow unified apps (and also updates the legacy clone-app and migrate-app commands to work with combined accounts)

See https://git.hubteam.com/HubSpot/hubspot-cli-issues/issues/806

Who to Notify

@brandenrodgers @kemmerle @joe-yeager

@camden11 camden11 changed the title Combined account legacy support Support legacy public app development in combined accounts Apr 23, 2025
@camden11 camden11 marked this pull request as ready for review April 23, 2025 16:31
Copy link
Contributor

@joe-yeager joe-yeager left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Comment on lines +88 to +91
export const FEATURES = {
UNIFIED_THEME_PREVIEW: 'cms:react:unifiedThemePreview',
UNIFIED_APPS: 'Developers:UnifiedApps:PrivateBeta',
} as const;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for moving these here 🙌

@camden11 camden11 merged commit 8ef5e82 into main Apr 23, 2025
1 check passed
@camden11 camden11 deleted the combined-account-legacy-support branch April 23, 2025 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants