From 715e15ff1464c206f926d5ba0603096803bd6cc7 Mon Sep 17 00:00:00 2001
From: nexdrew <andrewbgoode@gmail.com>
Date: Fri, 25 May 2018 07:36:21 -0400
Subject: [PATCH] chore(release): 2.0.0

---
 CHANGELOG.md | 15 +++++++++++++++
 package.json |  2 +-
 2 files changed, 16 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index fbaf12e..04ebf07 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,6 +2,21 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+<a name="2.0.0"></a>
+# [2.0.0](https://github.com/nexdrew/next-build-id/compare/v1.2.0...v2.0.0) (2018-05-25)
+
+
+### Features
+
+* use next-build-id as module within Next 6 generateBuildId function ([#6](https://github.com/nexdrew/next-build-id/issues/6)) ([502bccc](https://github.com/nexdrew/next-build-id/commit/502bccc))
+
+
+### BREAKING CHANGES
+
+* The next-build-id CLI has not changed, but module usage will no longer manually overwrite a BUILD_ID file unless a `write: true` option is given, so that the module can be used within generateBuildId from next.config.js to just lookup the current git commit hash.
+
+
+
 <a name="1.2.0"></a>
 # [1.2.0](https://github.com/nexdrew/next-build-id/compare/v1.1.0...v1.2.0) (2018-05-24)
 
diff --git a/package.json b/package.json
index b0e264d..24e18c9 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "next-build-id",
-  "version": "1.2.0",
+  "version": "2.0.0",
   "description": "Override `next build` output to use a consistent build id",
   "main": "index.js",
   "bin": "cli.js",