You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to see what had changed in this repository between the 1.0.1 npm release and the 2.2.1 npm release. So I used the following URL, which I expected to list all the commits:
Unfortunately, it didn't work, since this package does not have any release tags. Whatever process is used to release this to npm should ideally be updated to tag the release here in GitHub as part of the release process.
Even if things are tracked some other way, tags are the normal way to track releases with git, so I think they should be used.
The text was updated successfully, but these errors were encountered:
I wanted to see what had changed in this repository between the 1.0.1 npm release and the 2.2.1 npm release. So I used the following URL, which I expected to list all the commits:
1.0.1...2.2.1
Unfortunately, it didn't work, since this package does not have any release tags. Whatever process is used to release this to npm should ideally be updated to tag the release here in GitHub as part of the release process.
Even if things are tracked some other way, tags are the normal way to track releases with git, so I think they should be used.
The text was updated successfully, but these errors were encountered: