Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G gulp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gulp
  • gulp
  • Issues
  • #1486
Closed
Open
Issue created Jan 11, 2016 by Blaine Bublitz@phatedContributor

[Notice] gulp 4 release process

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

Assignee
Assign to
Time tracking