Skip to content

[Notice] gulp 4 release process #1486

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

Closed
phated opened this issue Jan 11, 2016 · 2 comments
Closed

[Notice] gulp 4 release process #1486

phated opened this issue Jan 11, 2016 · 2 comments

Comments

@phated
Copy link
Member

phated commented Jan 11, 2016

The gulp 4 release process will follow that of npm. That being, 4.0 will be released when there are no more breaking changes and will be released with the next tag. This allows users to continue to get 3.x when using npm install gulp or npm install gulp@latest but users that want to explicitly use gulp 4 can install with npm install gulp@next. When everything seems stable and well tested by users in their workflows, we will change the tag on gulp 4.x to latest.

Please note that we are not ready to release gulp 4 yet due to some outstanding breaking changes in vinyl-fs.

Thank you for your patience,
-The gulp team

@phated phated added the notice label Jan 11, 2016
@gulpjs gulpjs locked and limited conversation to collaborators Jan 11, 2016
@phated phated added this to the gulp 4 milestone Jan 11, 2016
@phated phated added the gulp4 label Jan 11, 2016
@phated
Copy link
Member Author

phated commented Jan 1, 2018

gulp 4 has been published under the next tag (npm install gulp@next) - We'll be working on the outstanding stuff - mostly docs - and any bugs before moving to the latest tag

@phated phated modified the milestones: gulp 4 - next tag, gulp 4 - latest tag Jan 1, 2018
@phated
Copy link
Member Author

phated commented Dec 10, 2018

We didn't get everything we wanted to for the "latest" tag but we're releasing it today.

https://medium.com/gulpjs/version-4-now-default-92c6cd4beb45

@phated phated closed this as completed Dec 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant