Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v4 to v5 Migration guide, wizard updates #356

Merged
merged 20 commits into from
Jan 27, 2025
Merged

v4 to v5 Migration guide, wizard updates #356

merged 20 commits into from
Jan 27, 2025

Conversation

ljstella
Copy link
Contributor

@ljstella ljstella commented Jan 24, 2025

Threw together some details around the largest changes to help folks migrate from v4 to v5 of contentctl.

Also merged in some updates to the new content wizard so it functions again.

@ljstella ljstella marked this pull request as ready for review January 24, 2025 18:20
@ljstella ljstella changed the title v4 to v5 Migration guide v4 to v5 Migration guide, wizard updates Jan 24, 2025
@pyth0n1c pyth0n1c added the 5.0 Targeted for ESCU 5.0 Release label Jan 27, 2025
@pyth0n1c
Copy link
Contributor

We should probably add a status: production as a default field to all newly created analytic stories.

Copy link
Contributor

@pyth0n1c pyth0n1c left a comment

Choose a reason for hiding this comment

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

Text and functionality of contentctl --new looks good here.

@pyth0n1c pyth0n1c merged commit 6625725 into main Jan 27, 2025
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5.0 Targeted for ESCU 5.0 Release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants