Update pdf2json: 1.1.7 → 1.2.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ pdf2json (1.1.7 → 1.2.0) · Repo

Commits

See the full diff on Github. The new version differs by 24 commits:

• MAINT: update node version
• MAINT: update depdencies and rebuild with merged PRs
• Merge pull request #181 from MasonVX/disable_cache_updated_file
• Merge branch 'master' into disable_cache_updated_file
• Merge pull request #199 from srijanshetty/password-api
• public API to set password for an encrypted PDF
• Merge pull request #193 from modesty/dependabot/npm_and_yarn/lodash-4.17.13
• Merge pull request #173 from kevin51jiang/master
• Merge branch 'master' into master
• build(deps): bump lodash from 4.17.11 to 4.17.13
• Merge pull request #174 from morfie78/master
• Merge branch 'master' into master
• Merge pull request #179 from escaleno-ltda/bugfix/async
• Merge pull request #189 from drabinowitz/update-lodash-4-17-15
• Update lodash to 4.17.15
• fix(deps): update async to v2.6.1 to remove vulnerabilities
• added check for newer file version
• Updated lodash to remove vulnerabilities
• Update p2j.forms.sh
• try removing the for loop
• Updated Version. 8.9.0 works well, but only in gitBash in admin mode.
• I hope this wasn't the problem
• Move back to 4.5.0
• modify travisCI

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #30.