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

Tag releases so it's installable with semver. #70

Closed
kitsunde opened this issue Oct 6, 2014 · 4 comments
Closed

Tag releases so it's installable with semver. #70

kitsunde opened this issue Oct 6, 2014 · 4 comments

Comments

@kitsunde
Copy link

kitsunde commented Oct 6, 2014

If you look at bower info devicejs compares to bower info underscore you'll notice there's no available versions. You need to do git push origin v0.1.16 or similar (see: http://bob.yexley.net/creating-and-maintaining-your-own-bower-package/)

Currently we have to pin our packages to a commit hash.

@catkins
Copy link

catkins commented Oct 7, 2014

+1

Also, without tags, I can't use the latest version with https://rails-assets.org

@matthewhudson
Copy link
Owner

@CelC @catkins

I don't happen to use bower so I apologize for dropping the ball. I've tagged the current version (0.1.16) and pushed using the following:

git tag -a v0.1.16 -m "Release version 0.1.16"
git push origin v0.1.16

This "flow" seems like something worth integrating with grunt release or perhaps a git hook. Does that sound about right to y'all?

@catkins
Copy link

catkins commented Oct 7, 2014

@matthewhudson Awesome, thanks! Works on rails-assets now.

@matthewhudson
Copy link
Owner

@CelC @catkins This is part of my general workflow going forward, and should be officially resolve as of v0.2.2

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

No branches or pull requests

3 participants