Skip to content

New "Upgrades" section (replaces updates & migration) for Strapi 5#2126

Merged
pwizla merged 15 commits intonextfrom
v5/migration-intro
Jun 24, 2024
Merged

New "Upgrades" section (replaces updates & migration) for Strapi 5#2126
pwizla merged 15 commits intonextfrom
v5/migration-intro

Conversation

@pwizla
Copy link
Collaborator

@pwizla pwizla commented Jun 13, 2024

This PR:

  • Fully reworks the old "updates & migration" section from v4.
  • Now uses the "upgrade" instead of updates or migration, as it both is more positive word (upgrading for something more recent and better) and is more consistent with the CLI tool name.
  • Provides a clear path whether you want to migrate from Strapi v4 or whether you simply want to learn about the upgrade tool (future-proof, will be used for upcoming versions after Strapi 5.0.0 is released)

Direct preview link: please start your journey 👉 here

@pwizla pwizla requested a review from meganelacheny as a code owner June 13, 2024 16:04
@vercel
Copy link

vercel bot commented Jun 13, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 19, 2024 8:44am

@strapi-cla
Copy link

strapi-cla commented Jun 13, 2024

CLA assistant check
All committers have signed the CLA.

@pwizla pwizla changed the base branch from main to next June 13, 2024 16:04
@pwizla pwizla self-assigned this Jun 13, 2024
@pwizla pwizla added the v5 Documentation PR that targets Strapi v5 label Jun 13, 2024
@pwizla pwizla added this to the 5.0.0 (stable) milestone Jun 13, 2024
@pwizla pwizla added the internal PRs created by the Strapi core team label Jun 13, 2024
@pwizla pwizla changed the title New "Upgrades" section (replaces updates & migration) New "Upgrades" section (replaces updates & migration) for Strapi 5 Jun 13, 2024
Copy link
Collaborator

@innerdvations innerdvations left a comment

Choose a reason for hiding this comment

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

LGTM, just some minor suggestions

const summaryStyle = {fontSize: '18px'}

# Migrating from Strapi v4 to Strapi 5
# Upgrading from Strapi v4 to Strapi 5
Copy link
Collaborator

Choose a reason for hiding this comment

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

Marketing question here, but mixing Strapi v4 and Strapi 5 sounds awkward and even a little confusing or like a typo. Would it make sense to retroactively call it Strapi 4?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good point, and why not, yes 🤷 But in this case I'll have to do it on each and every breaking change entry 😂

@pwizla pwizla merged commit f0160cc into next Jun 24, 2024
@pwizla pwizla deleted the v5/migration-intro branch June 24, 2024 15:39
@pwizla pwizla modified the milestones: 5.0.0 (stable), 5.0.0-rc.0 Jun 26, 2024
@pwizla pwizla modified the milestones: 5.0.0-rc.0, 5.0.0 (stable) Aug 13, 2024
@pwizla pwizla added pr: new content PRs for new product features or new documentation sections source: Dev Docs PRs/issues targeting the Developer Docs labels Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal PRs created by the Strapi core team pr: new content PRs for new product features or new documentation sections source: Dev Docs PRs/issues targeting the Developer Docs v5 Documentation PR that targets Strapi v5

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants