fix(CVE-2020-14001): Update kramdown to 2.3.0 #6564
Conversation
| # This will help ensure the proper Jekyll version is running. | ||
| # Happy Jekylling! | ||
| gem "jekyll", "~> 3.6.2" | ||
| gem "jekyll" |
There was a problem hiding this comment.
The Gemfile.lock reflects the version without explicitly setting it here.
This avoids transient problems with bundle update jekyll which won't do squat due to this pinning.
| kramdown (= 2.3.0) | ||
| kramdown-parser-gfm (= 1.1.0) |
There was a problem hiding this comment.
bundle update kramdown isn't sufficient due to jekyll's requirement of kramdown@1.
Codecov Report
@@ Coverage Diff @@
## main #6564 +/- ##
=======================================
Coverage 73.26% 73.26%
=======================================
Files 208 208
Lines 12920 12920
Branches 2525 2525
=======================================
Hits 9466 9466
Misses 3263 3263
Partials 191 191 Continue to review full report at Codecov.
|
* Got how to update from aws-amplify/amplify-js#6564
|
This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
3 participants
Issue #, if available:
Description of changes:
Updated
jekyll+github-pagesto latest, since they were using kramdown v1.Validated by running
bundle exec jekyll serveto check out site &yarn docsfor generating the/apipages.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.