Skip to content
This repository has been archived by the owner on Jul 26, 2022. It is now read-only.

An in-range update of prismjs is breaking the build 🚨 #210

Open
greenkeeper bot opened this issue Jan 13, 2020 · 1 comment
Open

An in-range update of prismjs is breaking the build 🚨 #210

greenkeeper bot opened this issue Jan 13, 2020 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jan 13, 2020

The optionalDependency prismjs was updated from 1.18.0 to 1.19.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prismjs is a optionalDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 26 commits.

  • 6fd5c96 1.19.0
  • 275366f Fix date in CHANGELOG
  • dc136fd Updated changelog for 1.19.0 (#2169)
  • 2a570fd OCaml: Improvements (#2179)
  • e5678a0 Updated gulp to v4.0.2 (#2178)
  • ef4d29d Handlebars: Added support for : and improved the variable pattern (#2172)
  • 543f04d Custom Class: Fixed TypeError when mapper is undefined (#2167)
  • c40d96c Added QML (#2139)
  • 99d979a SAS: Added CASL support (#2112)
  • fd857e7 JSX: Improved spread operator in tag attributes (#2159)
  • 8678045 Added missing .token selector (#2161)
  • 0b53913 Added checks for examples (#2128)
  • 0c2fe40 Custom Class: Fixed examples (#2160)
  • d7ad48f Markdown: Better language detection for code blocks (#2114)
  • 191b411 Added silent option to loadLanguages (#2147)

There are 26 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jan 13, 2020

After pinning to 1.18.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

0 participants