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

Inconsistent version control #1252

Open
robations opened this issue Aug 7, 2024 · 0 comments
Open

Inconsistent version control #1252

robations opened this issue Aug 7, 2024 · 0 comments

Comments

@robations
Copy link

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.)

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