Bump xml2js and chai-xml #14
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [xml2js](https://github.com/Leonidas-from-XIV/node-xml2js) to 0.5.0 and updates ancestor dependency [chai-xml](https://github.com/krampstudio/chai-xml). These dependencies need to be updated together. Updates `xml2js` from 0.4.23 to 0.5.0 - [Commits](https://github.com/Leonidas-from-XIV/node-xml2js/commits/0.5.0) Updates `chai-xml` from 0.3.2 to 0.4.1 - [Release notes](https://github.com/krampstudio/chai-xml/releases) - [Commits](krampstudio/chai-xml@0.3.2...0.4.1) --- updated-dependencies: - dependency-name: xml2js dependency-version: 0.5.0 dependency-type: indirect - dependency-name: chai-xml dependency-version: 0.4.1 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps xml2js to 0.5.0 and updates ancestor dependency chai-xml. These dependencies need to be updated together.
Updates
xml2jsfrom 0.4.23 to 0.5.0Commits
Updates
chai-xmlfrom 0.3.2 to 0.4.1Release notes
Sourced from chai-xml's releases.
Commits
efe69fachore: release 0.4.17eeff76Merge pull request #19 from krampstudio/18-update-dependenciesa013e56chore: update non breaking dep and dev depsdf804f9chore: version bump2c18a93Merge pull request #5 from fflorent/master9fc6eecMerge pull request #6 from krampstudio/feature/update-dependencies72b257aMerge remote-tracking branch 'origin/master' into feature/update-dependenciesfd8fc25Create node.js.yml5fdd0fdchore: update chai and move it as a peer depc1dfdc4fix: update xml2jsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.