Skip to content
New issue

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

sass-loader@4.0.1 untested ⚠️ #135

Merged
merged 1 commit into from
Sep 6, 2016
Merged

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

sass-loader just published its new version 4.0.1.

State No tests ⚠️
Dependency sass-loader
New version 4.0.1
Type dependency

This version is covered by your current version range, but I could not detect automated tests for this project. Without a test suite I can not really tell whether your project still works.

I was looking at the latest commit of your default branch, but GitHub said there is no status attached to it.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴


GitHub Release

  • Fix custom importers receiving 'stdin' as second argument instead of the actual resourcePath #267

The new version differs by 9 commits .

See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@alicoding alicoding force-pushed the greenkeeper-sass-loader-4.0.1 branch 3 times, most recently from e5da490 to 42549c4 Compare September 6, 2016 14:09
@alicoding alicoding merged commit f76648f into master Sep 6, 2016
@alicoding alicoding deleted the greenkeeper-sass-loader-4.0.1 branch September 6, 2016 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants