Inconsistent version control #1252
Description
I don't want to beat up anyone putting in time to maintain this package but I just wanted to note that there are confusing inconsistencies between the following:
- github releases (latest 3.4.1)
- tags (latest 3.4.3)
- changelog (latest 3.4.3)
- npm (latest 3.4.4)
Is there a way to automate the process?
You can regard this as a security risk to some extent, especially when there is compiled code deployed to npm that isn't readily available or visible within the published source code here. (Obviously there are bigger concerns within the node ecosystem in tracing package pedigree.)