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

feat(grunt-bower-release): support variety of options for tagging versions #45

Closed

Conversation

mikeborozdin
Copy link

This is a README.MD featuring the new configuration options.

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling 0d61e92 on NCR-CoDE:feature/gbr-35-readme into 2c75c2a on caitp:master.

@@ -79,8 +79,13 @@ It's super simple stuff, and I hope some people might find it useful!
3. `stageDir` -- A staging directory where the repository is built and tagged.
4. `main` -- Enables the grunt task to override `bower.json`'s `main` parameter. This will be ignored if it is not a string or an array.
5. `dependencies` -- Enables the grunt task to add dependencies to a build.
6. `extendDependencies` -- If true, the depencies from the source repository will be extended with the grunt options dependencies.
6. `extendDependencies` -- If true, the dependencies from the source repository will be extended with the grunt options dependencies.
Copy link
Owner

Choose a reason for hiding this comment

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

oops /).(\

@caitp caitp closed this in 2142407 May 30, 2014
@mikeborozdin
Copy link
Author

@caitp,

I wonder if we are going to publish a new version to the central NPM registry. At the moment, it still has an old one - https://www.npmjs.org/package/grunt-bower-release

@caitp
Copy link
Owner

caitp commented Jun 2, 2014

Yes --- but not right away. In the mean time, you can get the latest version by running npm install https://github.com/caitp/grunt-bower-release/tarball/master

@mikeborozdin
Copy link
Author

Cool. At the moment being we have to keep latest version in our private NPM registry, but ideally we would love to switch to the one that is in the central NPM registry.

@mikeborozdin
Copy link
Author

@caitp,

Do you think it will make into the central NPM registry anytime soon?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants