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

Releases to npm don't appear to be tracked in any way #141

Open
tcobbs-bentley opened this issue Oct 26, 2022 · 0 comments
Open

Releases to npm don't appear to be tracked in any way #141

tcobbs-bentley opened this issue Oct 26, 2022 · 0 comments

Comments

@tcobbs-bentley
Copy link
Member

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.

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

1 participant