Create a version task #874
Conversation
Add a new grunt task to create a new release version. It can be run like this: grunt dist version:patch Running dist before the version task is required so the build artifacts are available. The task uses `npm version` to bump the package version, copies the new version into the bower file and then force commits the dist directory in one shot. If that's successful, the dist directory is deleted in another commit so that no one accidentally makes patches against those files.
|
Might as well add a |
|
Well, the nice thing about this version is it only messes with your local repo so you get the choice of how you want to publish it. I'd like to be able to make patched versions of video.js occasionally for testing but I don't necessarily want to push it out to my fork. |
|
Yep, the publish should be another task. |
|
Very cool. Could this possibly be broken up into even smaller tasks. I'm already using other versioning processes in contribflow that include things like changelog updates as well, and I'll need to figure out how to work them together. |
Create three smaller release tasks: check-for-changes, version, and commit-version. Add a roll-up task to execute them in the proper order. To create a minor release, you would run: grunt release --type=minor
If no npmignore is present, npm will fall back on the gitignore. Our gitignore ignores dist/, which is the exact opposite of what we want npm to do. Adding an explicit npmignore overrides the settings for git. This one is based on the gitignore, with dist/ removed and some entries which appeared to be for older layouts of the repo.
|
Going to use the version of this that's going into the swf. |
Add a new grunt task to create a new release version. It can be run like this:
Running dist before the version task is required so the build artifacts are available. The task uses
npm versionto bump the package version, copies the new version into the bower file and then force commits the dist directory in one shot. If that's successful, the dist directory is deleted in another commit so that no one accidentally makes patches against those files.With the bower.json file now directly in the repo, I think it should be possible to retire video.js-component