An in-range update of autoprefixer is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Version 6.7.3 of autoprefixer just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | autoprefixer |
| Current Version | 6.7.2 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As autoprefixer is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Status Details
Release Notes
6.7.3- Fix compatibility with “Intrinsic & Extrinsic Sizing” spec update.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the greenkeeper/autoprefixer-6.7.3 branch and the failed CircleCI and AppVeyor build details linked in the issue. Identify the build failure caused by autoprefixer 6.7.3; the work is done when the project builds and its checks pass with the dependency update or an appropriate resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100