diff --git a/CHANGELOG.md b/CHANGELOG.md
index 0be510d..ac721f9 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,7 @@
+## 1.6.0
+- Adds `resolvePathsRelativeToConfig` to the config options to allow paths to be resolved relative to your config file rather than project root. Thanks to [@DirtyHairy](https://github.com/DirtyHairy)
+- The usual third party package updates
+
 ## 1.5.0
 - Allows the inclusion of files with extra extensions such as 'file.scss.liquid'
 - Updated to Atom linter ^5.0.1
diff --git a/README.md b/README.md
index 9d7d5ac..44fb865 100644
--- a/README.md
+++ b/README.md
@@ -46,6 +46,8 @@ There are three options you can configure either within the plugin or by editing
 
 * `globalSassLint` This allows you to specify that you want to use your globally installed version of `sass-lint` (`npm install -g sass-lint`) instead of the version bundled with `linter-sass-lint`.
 
+* `resolvePathsRelativeToConfig` This option allows you to choose to resolve file paths relative to your config file rather than relative to the root of your currently open project.
+
 ### Extra File Extensions
 
 This plugin will attempt to lint a file with framework specific file extensions on top of the usual `.scss` and `.sass` extensions such as with shopify's `.scss.liquid` extension as long as you still include `.scss` or `.sass` somewhere in the file, you must also ensure that the Atom grammar scope for that file is set to either SCSS or Sass depending on which it corresponds to.