Update html-proofer: 3.14.1 → 3.15.3 (minor)

[depfu]

---

Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!

---

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?

✳️ html-proofer (3.14.1 → 3.15.3) · Repo

Release Notes

3.15.0

• #362

Does any of this look wrong? Please let us know.

Commits

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

• :gem: bump to 3.15.3
• Merge pull request #556 from riccardoporreca/fix-recheck-failure
• Merge branch 'master' into fix-recheck-failure
• :gem: bump to 3.15.2
• Merge pull request #560 from gjtorikian/leave-semicolon-attr
• Fix tests
• Ruby 2.3 is gone
• tr away semicolons
• Report on errors here
• ticks
• Provide Timecop updates
• Test alias
• Merge pull request #555 from gjtorikian/parse-failure
• crap, this should always have been on
• not sure why this is not printing properly
• Add more error options
• Assert HTML failures are reported
• minor - improve comments
• No extra empty line detected at block body beginning/end.
• Fix recheck of failures.
• Fix and simplify cache tests on existing URL.
• Merge pull request #551 from dsinn/patch-1
• Minor grammar fix
• Update CODEOWNERS
• :gem: bump to 3.15.1
• Merge pull request #550 from gjtorikian/new-ruby-issues
• Ah Rubocop
• Fix logging issues
• Demonstrate 2.7 break
• Hide vendor/cache
• :gem: bump to 3.15.0
• Merge pull request #362 from jeremy/html5
• rubocop!!
• Add missing docs
• Slight gem fixes
• Add doctype to valid doc fixture
• rubocop
• Merge branch 'master' into html5
• CI trigger?
• Report errors

↗️ ffi (indirect, 1.11.2 → 1.12.2) · Repo · Changelog

Release Notes

1.12.2 (from changelog)

• Fix possible segfault at FFI::Struct#[] and []= after GC.compact . #742

1.12.1 (from changelog)

Added:

• Add binary gem support for ruby-2.7 on Windows

1.12.0 (from changelog)

Added:

• FFI::VERSION is defined as part of require 'ffi' now. It is no longer necessary to require 'ffi/version' .

Changed:

• Update libffi to latest master.

Deprecated:

• Overwriting struct layouts is now warned and will be disallowed in ffi-2.0. #734, #735

1.11.3 (from changelog)

Removed:

• Remove support for tainted objects which cause deprecation warnings in ruby-2.7. #730

Does any of this look wrong? Please let us know.

Commits

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

• Bump VERSION to 1.12.2
• Update CHANGELOG for 1.12.2
• Replace st_table with simple cache and fix segfault after GC.compact
• Remove old references to ruby-1.9
• Bump VERSION to 1.12.1
• Do parallel builds in CI docker containers
• Respect MAKE environment variable for libtest build
• Better document enable/disable libffi switches in the README
• Bump VERSION to 1.12.0
• Update CHANGELOG for version 1.12.0
• Update libffi to latest master branch
• Merge pull request #735 from larskanis/disallow-re-layout
• Warn about Struct layout redefinition only
• Namespace all benchmarks since they are loaded into one process
• Disallow struct layout changes
• Require "ffi/version" per default
• Set ruby-2.3.8 to allow_failures because of ffi unrelated error
• Update rake to avoid warnings on ruby-2.7
• Update to rake-compiler-dock-1.0.0 to build ruby-2.7 binary gems
• Bump VERSION to 1.11.3
• Prepare CHANGELOG for 1.11.3
• Merge branch 'y-yagi-remove_taint_support'
• Remove taint support

↗️ nokogiri (indirect, 1.10.5 → 1.10.9) · Repo · Changelog

Release Notes

1.10.9

1.10.9 / 2020-03-01

Fixed

• [MRI] Raise an exception when Nokogiri detects a specific libxml2 edge case involving blank Schema nodes wrapped by Ruby objects that would cause a segfault. Currently no fix is available upstream, so we're preventing a dangerous operation and informing users to code around it if possible. [#1985, #2001]
• [JRuby] Change NodeSet#to_a to return a RubyArray instead of Object, for compilation under JRuby 9.2.9 and later. [#1968, #1969] (Thanks, @headius!)

1.10.8

1.10.8 / 2020-02-10

Security

[MRI] Pulled in upstream patch from libxml that addresses CVE-2020-7595. Full details are available in #1992. Note that this patch is not yet (as of 2020-02-10) in an upstream release of libxml.

1.10.7

1.10.7 / 2019-12-03

Bug

• [MRI] Ensure the patch applied in v1.10.6 works with GNU patch. [#1954]

1.10.6

1.10.6 / 2019-12-03

Bug

• [MRI] Fix FreeBSD installation of vendored libxml2. [#1941, #1953] (Thanks, @nurse!)

Does any of this look wrong? Please let us know.

Commits

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

• version bump to v1.10.9
• update CHANGELOG
• Change return type to RubyArray
• update CHANGELOG for #1985
• Work around a bug in libxml2
• version bump to v1.10.8
• update CHANGELOG for v1.10.8
• remove patches from the hoe Manifest
• update to use rake-compiler ~1.1.0
• backport libxml2 patch for CVE-2020-7595
• version bump to v1.10.7
• update CHANGELOG
• Fix the patch from #1953 to work with both `git` and `patch`
• Fix typo in generated metadata
• add gem metadata
• version bump to v1.10.6
• update CHANGELOG
• Add a patch to fix libxml2.la's path
• add security note to CHANGELOG

↗️ parallel (indirect, 1.19.0 → 1.19.1) · Repo

Commits

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

• v1.19.1
• Merge pull request #271 from grosser/grosser/exc
• rescue core exceptions like rspec does
• Merge pull request #270 from orien/gem-metadata
• Documentation is the readme
• Add project metadata to the gemspec

↗️ yell (indirect, 2.2.0 → 2.2.2) · Repo

Sorry, we couldn't find anything useful about this release.

🆕 nokogumbo (added, 2.0.2)

---

👉 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)

[github-learning-lab]

I was expecting your file to be named _posts/0000-01-02-AnjaPrivat.md.

Let's edit this pull request to fix both of these issues.

⌨️ Activity: Fixing your pull request

1. Click the Files Changed tab in this pull request
2. Verify that the only file edited is named _posts/0000-01-02-AnjaPrivat.md.
3. If the file is improperly named, or not in a proper location, use the edit function to correct it.
4. Above the contents of the file, select all text in the field that contains the filename and delete it.
5. Continue pressing your backspace key to also delete any directory names that exist.
6. Type the proper filename:

   _posts/0000-01-02-AnjaPrivat.md

7. Scroll to the bottom and enter a commit message and commit in the Commit Changes section.

Note: Can't find the button to edit the file? It may look like a pencil, or it may look like three dots.

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.

---

I'll respond below when I detect a commit on this branch.

[depfu]

Closed in favor of #15.