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

v4.1.0 has not been published to npm #36

Open
ghost opened this issue Mar 17, 2020 · 6 comments
Open

v4.1.0 has not been published to npm #36

ghost opened this issue Mar 17, 2020 · 6 comments

Comments

@ghost
Copy link

ghost commented Mar 17, 2020

Hi!

I see that v4.1.0 hasn't been published on npm. Are there any issues preventing this new minor release?

@epiccoolguy
Copy link

@jonschlinkert Would love to know if there's anything you need help with to publish the version with types exported! For now we're using the package from sources.

yoursunny added a commit to yoursunny/NDNts that referenced this issue May 8, 2020
@dkebler
Copy link

dkebler commented May 2, 2021

Hmm.... npm has 2.0. Not sure why newer tags are not being published?

@dkebler
Copy link

dkebler commented May 2, 2021

while at it set-value and get-value can be updated.

@yoursunny
Copy link
Contributor

while at it set-value and get-value can be updated.

NPM is now complaining about some vulnerability in set-value.

set-value  <4.0.1
Severity: high
Prototype Pollution in set-value - https://github.com/advisories/GHSA-4jqc-8m5r-9rpr
No fix available
node_modules/set-value
  data-store  0.4.0 - 0.9.0 || >=4.0.0
  Depends on vulnerable versions of set-value

@Brittany-Reid
Copy link

I've added a pull request to fix vulnerabilities, however, there was a failing test case. Hopefully that gets things moving.

@helderjnpinto
Copy link

Hey is needed some help to get this moving ?

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

5 participants