Publish v2.0.0

- **Breaking: You must change your `netlify.toml` configuration for
  next-on-netlify v2.0.0.** Please look at the README for the latest
  configuration.
  `next-on-netlify` now builds pre-rendered pages and static assets in
  `out_publish`. Netlify Functions for SSR pages are built to
  `out_functions`.
- Add support for `getStaticProps` (#7)
- Add support for `getStaticPaths` with and without fallback (#7)
- Add support for `getServerSideProps` (#7)
- Query string parameters are now correctly passed to Next Pages and API
  endpoints (#9)
- Response headers are now correctly set (#9)
- When a user encounters a 404, `next-on-netlify` now display the NextJS
  404 page rather than Netlify's default 404 page. You can customize the
  NextJS 404 page. (#2)
- Every page with server-side rendering is now converted to a
  stand-alone Netlify Function. Previously, all SSR pages were bundled
  in a single Netlify Function.
- `next-on-netlify` now prints out which pages are being converted to
  Netlify Functions for SSR, which pages are served as pre-rendered
  HTML, and the redirects that are being generated.
- Adding custom redirects via a `_redirects` file in the project root is
  no longer supported. Let me know if you want this back. Or define your
  redirects in `netlify.toml`.

Author: FinnWoelm

CHANGELOG.md

@@ -1,5 +1,20 @@
 # Changelog
 
+## 2.0.0 (2020-06-02)
+
+- **Breaking: You must change your `netlify.toml` configuration for next-on-netlify v2.0.0.** Please [look at the README](https://github.com/FinnWoelm/next-on-netlify#3-configure-netlify) for the latest configuration.  
+`next-on-netlify` now builds pre-rendered pages and static assets in `out_publish`. Netlify Functions for SSR pages are built to `out_functions`.
+- Add support for `getStaticProps` ([#7](https://github.com/FinnWoelm/next-on-netlify/issues/7))
+- Add support for `getStaticPaths` with and without fallback ([#7](https://github.com/FinnWoelm/next-on-netlify/issues/7))
+- Add support for `getServerSideProps` ([#7](https://github.com/FinnWoelm/next-on-netlify/issues/7))
+- Query string parameters are now correctly passed to Next Pages and API endpoints ([#9](https://github.com/FinnWoelm/next-on-netlify/issues/9))
+- Response headers are now correctly set ([#9](https://github.com/FinnWoelm/next-on-netlify/issues/9#issuecomment-633288179))
+- When a user encounters a 404, `next-on-netlify` now display the NextJS 404 page rather than Netlify's default 404 page. You can [customize the NextJS 404 page](https://nextjs.org/docs/advanced-features/custom-error-page#customizing-the-404-page).
+ ([#2](https://github.com/FinnWoelm/next-on-netlify/issues/2))
+- Every page with server-side rendering is now converted to a stand-alone Netlify Function. Previously, all SSR pages were bundled in a single Netlify Function.
+- `next-on-netlify` now prints out which pages are being converted to Netlify Functions for SSR, which pages are served as pre-rendered HTML, and the redirects that are being generated.
+- Adding custom redirects via a `_redirects` file in the project root is no longer supported. Let me know if you want this back. Or define your redirects in `netlify.toml`.
+
 ## 1.2.0 (2020-04-26)
 
 - Add support for custom NextJS build directory: If `distDir` is specified in

package.json

@@ -1,6 +1,6 @@
 {
   "name": "next-on-netlify",
-  "version": "1.2.0",
+  "version": "2.0.0",
   "description": "Wrapper for hosting NextJS applications with Server-Side Rendering on Netlify",
   "bin": "./next-on-netlify.js",
   "keywords": [