-
Notifications
You must be signed in to change notification settings - Fork 123
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
Upgrade xlmdom dependency to fix security advisory #110
Comments
I think maybe there is some confusion. xmldom hasn't published a 0.7.0 version yet. Are you referring to something else? |
They did but only as github release (repo update), not published on npm yet. @sofiyaca, the |
ahhhh, it appears a I updated the xmldom dep a few weeks ago, but never published it to npm. Will do that now. |
It's live as 3.0.3. |
This should be reopened. plist 3.0.3 bumped xmldom to |
As of right now, there is no such thing as xmldom@0.7.0. See here: https://www.npmjs.com/package/xmldom The latest module published is 0.6.0. When xmldom publishes this, we'll update. |
Right, I missed leading zero.
There is going to be xmldom 0.6.1 release xmldom/xmldom#270 (reply in thread) so new plist release won't be required. |
Just out of curiosity, does anyone know why the xmldom people are not able to publish 0.7.0 to npm? They mention they're having trouble in the issue but not where this trouble is coming from. Seems very...odd... |
Some info recently posted here xmldom/xmldom#271 (comment) |
Looks like they will be publishing a new version of xmldom called @xmldom. I believe it should be published later today with the fix |
https://www.npmjs.com/package/@xmldom/xmldom It is published. |
fixed via fa8e184 |
…ixes TooTallNate#110, TooTallNate#111" This reverts commit fa8e184.
The dependency on xlmdom listed in package.json has a vulnerability. Can the version restriction be upgraded to allow the fixed version 0.7.0?
The text was updated successfully, but these errors were encountered: