We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using Jekyll version 4.1.0 (which was released the other day) breaks Travis tests. The .travis.yml file should lockdown Jekyll to ~> 4.0.0 or fix the tests: https://github.com/jekyll/jekyll-seo-tag/blob/master/.travis.yml#L18.
.travis.yml
~> 4.0.0
Long story short, I was fiddling around with a fork, and found that the later version breaks: https://travis-ci.com/github/emma-sax4/jekyll-seo-tag/builds/168817663. But locking down Travis succeeds again: https://travis-ci.com/github/emma-sax4/jekyll-seo-tag/builds/168820682.
The text was updated successfully, but these errors were encountered:
@emmasax4 Jekyll 4.1.1 has been shipped. Can you verify if this is still an issue? Thanks.
Sorry, something went wrong.
Yep, the issue is resolved now. I'll make a pull request to lock down the version of Jekyll that Travis uses.
No branches or pull requests
Using Jekyll version 4.1.0 (which was released the other day) breaks Travis tests. The
.travis.yml
file should lockdown Jekyll to~> 4.0.0
or fix the tests: https://github.com/jekyll/jekyll-seo-tag/blob/master/.travis.yml#L18.Long story short, I was fiddling around with a fork, and found that the later version breaks: https://travis-ci.com/github/emma-sax4/jekyll-seo-tag/builds/168817663. But locking down Travis succeeds again: https://travis-ci.com/github/emma-sax4/jekyll-seo-tag/builds/168820682.
The text was updated successfully, but these errors were encountered: