-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Releases and tags missing #1273
Comments
I don't think adding git tags for NPM releases is that important, personally. |
It makes it nice when you're trying to track down if a commit has landed in a certain version, as the most immediate usecase. And if it's easily automatable/added to the 'deploy' scripts, then you kind of get it 'for free'. This seems to have been raised previously, and according to the outcome of that issue, was accepted as 'we should do that':
|
There's no "deploy script" unfortunately. It's a pretty manual process. I can try to remember to do this, but I make no promises. |
Would it be worth wrapping up the process into a deploy/'release' script of sorts, save having to remember? |
I still don't think tags are very valuable in this repo, so in my opinion– no. |
Closing this for now. I'll try to remember to git tag when I create releases. |
(Ref: #1207 (comment))
Looks like there have been no releases since
v3.4.2
, and no git tags sincev3.3.2
, even though master seems to have commits naming versions up tov3.6
currently:Was wondering when there is likely to be releases for these intermediary versions, and if the tags could also be updated to match.
Edit: It seems this also doesn't match what is live in the chrome store, as that version appears to be
v6.0
:The text was updated successfully, but these errors were encountered: