[BUG] Revert xmldom github reference to standard version string #243
Comments
brent-spiner
pushed a commit
that referenced
this issue
Sep 7, 2021
## [4.0.31](v4.0.30...v4.0.31) (2021-09-07) ### Bug Fixes * Make caching class return undefined if property does not exist ([#247](#247)) ([8e3b3ad](8e3b3ad)) * use newer node version in CI release process, required to run semantic-release. ([589e0ce](589e0ce)) * use newly published @xmldom/xmldom package. fixes [#243](#243) ([9f8b646](9f8b646))
|
🎉 This issue has been resolved in version 4.0.31 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To fix a security vulnerability, we needed to update to a version of
xmldomthat is not yet published on npmjs.com.After
xmldom 0.7.0is published, we should revert thepackage.jsonversion to a standard version string, as in remove this github version and replace it with a standard version string (like:'^0.7.0') whenxmldom 0.7.0is published to npmjs.com.Relates to PR #242
See: xmldom/xmldom#270
cc @bhamail / @DarthHater / @allenhsieh / @Slim-Shary
The text was updated successfully, but these errors were encountered: