Skip to content
This repository has been archived by the owner on Jan 19, 2020. It is now read-only.

Tag Releases #8

Open
jcampbell05 opened this issue Sep 16, 2016 · 4 comments
Open

Tag Releases #8

jcampbell05 opened this issue Sep 16, 2016 · 4 comments

Comments

@jcampbell05
Copy link
Collaborator

I should start tagging new releases and look into if it's possible to retroactively tag older versions.

@vutran
Copy link
Member

vutran commented Oct 12, 2016

We should be able to do this by specifying the commit's checksum...

Sample commit: 3a7bfbc

$ git tag -a v1.0.0 3a7bfbc

@jcampbell05
Copy link
Collaborator Author

@vutran is there a way to figure out the commit for a NPM _ackage ?

@vutran
Copy link
Member

vutran commented Oct 12, 2016

npm usually reads from the version specified from package.json.

If you've been using npm version <something> to bump, it should have automatically created git tags locally as well as a new commit that bumps the version in package.json. It makes it really easy to see where the tag points are in the commit history.

@jcampbell05
Copy link
Collaborator Author

Cool will try that in future :) and will have to manually tag the older releases I guess.

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

No branches or pull requests

2 participants