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

docs: remove specific Nuxt 4 release date #29151

Merged
merged 2 commits into from
Sep 25, 2024
Merged

Conversation

selfire1
Copy link
Contributor

@selfire1 selfire1 commented Sep 25, 2024

https://nuxt.com/docs/getting-started/upgrade

📚 Description

Currently, the documentation states that Nuxt 4 is planned to be released "on or before June 14". Those of us who are plugged in to the Nuxt community are aware that the actual timeline is "to be announced" (as detailed in #27716).

But for people new to Nuxt, or those who don't check the announcements that often, this might be confusing. One might think "June 14th has passed for a while – is it simply delayed? Or do the authors mean 2025? Am I safe to use Nuxt now or should I wait for v4?"

I think removing the specific date for the Nuxt 4 release in favour of a "to be announced" might clarify that confusion.

updates the timeline according to nuxt#27716
@selfire1 selfire1 requested a review from danielroe as a code owner September 25, 2024 03:26
Copy link

stackblitz bot commented Sep 25, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link
Member

@danielroe danielroe left a comment

Choose a reason for hiding this comment

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

thank you ❤️

@danielroe danielroe merged commit ed7f946 into nuxt:main Sep 25, 2024
5 of 6 checks passed
@github-actions github-actions bot mentioned this pull request Sep 25, 2024
@github-actions github-actions bot mentioned this pull request Sep 25, 2024
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants