Bump tough-cookie and regjsparser #332
Open
Conversation
This file contains 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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Removes [tough-cookie](https://github.com/salesforce/tough-cookie). It's no longer used after updating ancestor dependency [regjsparser](https://github.com/jviereck/regjsparser). These dependencies need to be updated together. Removes `tough-cookie` Updates `regjsparser` from 0.4.0 to 0.10.0 - [Release notes](https://github.com/jviereck/regjsparser/releases) - [Changelog](https://github.com/jviereck/regjsparser/blob/gh-pages/CHANGELOG) - [Commits](jviereck/regjsparser@v0.4.0...v0.10.0) --- updated-dependencies: - dependency-name: tough-cookie dependency-type: indirect - dependency-name: regjsparser dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
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.
Removes tough-cookie. It's no longer used after updating ancestor dependency regjsparser. These dependencies need to be updated together.
Removes
tough-cookieUpdates
regjsparserfrom 0.4.0 to 0.10.0Release notes
Sourced from regjsparser's releases.
... (truncated)
Commits
c622da7Release v0.10.0371fc27Merge pull request #131 from jviereck/jviereck_fix_1300160157Allow "Anchor Quantifier" within Termsd58221dBump package.json to v0.9.16faf49cMerge pull request #129 from liuxingbaoyu/gh-pages38c6076fix modifiers5215b8dMerge pull request #128 from liuxingbaoyu/eslint-indent5b94203fixace5e55Bump package version to 0.9.0524fbd5Merge pull request #127 from liuxingbaoyu/modifiersDependabot 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 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.