v0.11.5

This is the latest release with support for Terraform AWS Provider v3.x.
Upcoming releases require at least >= 4.8.

Changelog

• Adds support for route-manifest v4 (#292)
  This ensures the builder works with Next.js versions >= v12.1.3.
• Restrict image optimizer submodule version to <= v12.0.10 (#293)
  Since the v12.0.10 release is the last version with support for Terraform AWS Provider v3.x this update ensures existing setups will not break in the future.
• Bump @vercel/build-utils from 2.10.1 to 2.12.1 (#287)

v0.11.4

Changelog

Fixed

• Determine content-type correctly for localized pre-rendered HTML pages (#278, #277)

v0.11.3

Changelog

• Adds new output for Lambda role ARNs lambda_execution_role_arns (#270)

v0.11.2

Changelog

Added

• Support for response headers policy (cloudfront_response_headers_policy) for the internal CloudFront distribution (#265, #268)
  This also increases the minimum required Terraform AWS provider version from 3.43.0 to 3.64.0.

Fixed

• Bash script for uploading assets to S3 now uses the standard endpoint and is now compatible with newer AWS regions (#263)
• Components fetched from npm registry now use relative paths that are stored in the Terraform state, which prevents unnecessary deployments (#261)

New Contributors

• @exodusanto made their first contribution in #263
• @aquanow-jeffen made their first contribution in #265

v0.11.1

Changelog

Fixed

• Fix for cloudfront invalidation dynamic routing paths (#258)

New Contributors

• @ky0615 made their first contribution in #258

v0.11.0

Changelog

Added

• Option for attaching a waf policy to the internal CloudFront distribution (#250)

Changed

• TTL for Cache-Control header is set to 0 (no cache) when the header is not sent from origin (#241, #236, #254)

Fixed

• Static routes were falsely generated when running on Windows (#246)

v0.10.2

Bugfix release that ensures compatibility with the v12.0.0 version of the Terraform Next.js Image Optimization module for AWS.

Changelog

• create_image_optimization breaks because of breaking change in the newest 12.0.0 release (#243, #244)

New Contributors

• @mohalsherif made their first contribution in #244

v0.10.1

This release ensures that static generated routes with dynamic parts (e.g. /test/[...slug]) are invalidated correctly when running terraform apply.
We also added a new option to define tags exclusively on S3 buckets created by this module.

Changelog

• Ensure correct invalidation for slug paths (#140, #229, #228)
• Adds new input variable tags_s3_bucket (#216, #230)

v0.10.0

Beginning with this release we streamline the versioning of the Terraform module with its npm-packages.
So when you use the Terraform module in version 0.10.0 you should also use the [email protected] npm-package for building the Next.js project.

This release also increases the minimum required Terraform version from 0.13 to 0.15.

Changelog

• Forward correct host header to server-side rendered pages (#156, #161)
• Adds charset to Content-Type header for static routes and files served by S3 (#214, #226)
• Removes empty provider warning when running Terraform commands (#155, #219)
• Removes random ids from resource names (#212, #227)

v0.9.3

This release fixes the routing behavior for dynamic routes that are statically generated (served from S3).

Changelog

Proxy

• Fixes dynamic routing for statically generated routes (#218, #221)