Skip to content

Latest commit

 

History

History
251 lines (156 loc) · 17 KB

CHANGELOG.md

File metadata and controls

251 lines (156 loc) · 17 KB
Raw

Changelog

[Unreleased]

[12.1.3] - 2022-08-12

  • Uses Image Optimizer module of Next.js 12.1.3 (#121)
  • Updates sharp from v0.30.3 to v0.30.7 (#136)
  • Support usage of custom domain and SSL certificate with the default CloudFront distribution (#134)
  • Minimum protocol version for the default CloudFront distribution can now set using cloudfront_minimum_protocol_version variable. New default value is TLSv1 (was TLSv1.2_2018 before) (#134)

[12.1.2] - 2022-04-16

[12.1.1] - 2022-04-13

[12.1.0] - 2022-04-04

  • Ensure compatibility with AWS Provider Version 4 (#119, #120)
  • Uses Image Optimizer module of Next.js 12.1.0 (#123)
  • Adds option to enable SVG support (#124)

[12.0.10] - 2022-03-29

[12.0.9] - 2022-02-17

  • Uses Image Optimizer module of Next.js 12.0.9 (#104)
  • Smaller and better optimized image optimizer package (#113)

[12.0.8] - 2022-02-17

[12.0.7] - 2022-02-15

[12.0.6] - 2022-01-29

[12.0.5] - 2022-01-22

[12.0.4] - 2022-01-22

[12.0.3] - 2022-01-22

[12.0.2] - 2022-01-22

  • Uses Image Optimizer module of Next.js 12.0.2 (#101)
  • Use relative path as lambda function local package path (#98)

[12.0.1] (December 21, 2021)

In this release we fixed a bug that could occur when using absolute image paths (When you use S3 as backend, you are not affected).
In addition you can now define a new input variable next_image_base_origin that can be used to resolve absolute image paths.

When you set next_image_base_origin = "https://example.com" requests for an absolute image path (/path/to/image.png) are then resolved to the URL https://example.com/path/to/image.png.

We also added a fully featured example how to use next export together with S3 and the image optimizer, check it out: Statically exported Next.js app hosted on S3

12.0.0 (November 28, 2021)

This release introduces a new package called Pixel that abstracts the image optimization stuff and makes it usable with platforms other than AWS Lambda. We plan to offer multiple flavors of it, like express middleware or docker images.

⚠️ Breaking Changes ⚠️

We have removed the output variable cloudfront_origin_image_optimizer that was deprecated since the v11.0.0 release. To upgrade, please use the output variable cloudfront_origin from now on.

E.g. when using the "With existing CloudFront distribution example" you should make the following changes:

module "next_image_optimizer" {
  source = "milliHQ/next-js-image-optimization/aws"
  ...
}

resource "aws_cloudfront_distribution" "distribution" {
  ...

  dynamic "origin" {
-   for_each = [module.next_image_optimizer.cloudfront_origin_image_optimizer]
+   for_each = [module.next_image_optimizer.cloudfront_origin]
   ...
  }
}
  • Uses Image Optimizer module of Next.js 12.0.0 (#80)
  • Add support for AVIF (#73, #92)
  • Fixes "Error while trying to add new domain" bug (#68, #69)
  • Remove random strings from resource names (#72, #77)
  • Bump sharp from 0.29.1 to 0.29.3 (#79, #85)
  • Remove deprecated output cloudfront_origin_image_optimizer (#78, #82)
  • Remove referer header from cache key when S3 is used (#87, #91)

11.1.2 (September 14, 2021)

11.1.1 (September 02, 2021)

The upgrade to Next.js 11.1.1 fixes a potential vulnerability which allowed a XSS-attack. For more information see the Security Advisory.

11.1.0 (August 30, 2021)

⚠️ Namespace changed ⚠️

We recently changed the namespace of this module from dealmore to milliHQ. Make sure to upgrade the source of the module accordingly:

module "next_image_optimizer" {
-  source = "dealmore/next-js-image-optimization/aws"
+  source = "milliHQ/next-js-image-optimization/aws"
}

Beginning with this release we change the engine that is used to optimize the images from squoosh to Sharp. Sharp has a much better performance and is therefore better suited for the job. Please read the Next.js RFC for more information.

  • Use sharp as image optimization engine (#51, #57)
  • Fix typo for default image sizes (#53, #56)
  • Uses Image Optimizer module of Next.js 11.1.0 (#54)

11.0.1 (July 06, 2021)

11.0.0 (June 15, 2021)

The output cloudfront_origin_image_optimizer is now deprecated. Use cloudfront_origin instead.

  • Fixes image optimization for webp format (#44)
    Thanks to @vcnc-hex for contributing!
  • Uses Image Optimizer module of Next.js 11.0.0 (#45)
  • Add output for cache behavior (#43, #48)
  • Bump AWS API Gateway Terraform module from 0.11.0 to 1.1.0 (#47)
  • Bump AWS Lambda Terraform module from 1.47.0 to 2.4.0 (#46)

10.2.3 (June 05, 2021)

10.2.2 (May 22, 2021)

10.2.1 (May 22, 2021)

10.2.0 (May 11, 2021)

10.1.3 (May 11, 2021)

10.1.2 (May 04, 2021)

10.1.1 (May 04, 2021)

10.1.0 (May 04, 2021)

10.0.9 (April 27, 2021)

10.0.8 (April 26, 2021)

10.0.7 (April 01, 2021)

10.0.6 (April 01, 2021)

  • Uses Image Optimizer module of Next.js 10.0.6 (#3)
  • Bundling of the image optimizer has changed from ncc to nft (#23, #24)

10.0.5 (March 15, 2021)

Note 1: From now on we aligning the versioning schema with the releases of Next.js.

Note 2: When upgrading from a previous release, you may experience an error from Terraform:

Error: error updating CloudFront Distribution:
InvalidArgument: The parameter ForwardedValues cannot be used when a cache policy is associated to the cache behavior.
	status code: 400

This is a known bug in the Terraform AWS provider and may requires a manual upgrade in the AWS Console (terraform-provider-aws#17626).

  • Fixes wrong response for repeated requests from external source (#12, #13)
  • Use Request and Cache Policies in CloudFront distribution (#5, #9)
  • Upgrades Lambda runtime from nodejs12.x to nodejs14.x. (#4, #8)

2.0.1 (March 08, 2021)

  • Bump internal module terraform-aws-modules/apigateway-v2/aws from 0.8.0 to 0.11.0 (#16, #18)
    Resolves compatibility issue with newer versions of Terraform.

2.0.0 (February 13, 2021)

  • Adds support to resize images from a S3 origin (#7)

1.0.0 (February 07, 2021)

Initial release