v1.0.0-canary.5

This release fixes a bug with the --profile (or --awsProfile) flag in the CLI.

Changelog

• Adds alias for profile, improves error message (#344)

v1.0.0-canary.4

Bugfix release that fixes issues with the installation.

v1.0.0-canary.3

This release fixes various bugs with the CLI and improves its usability.
The CloudFormation stacks now use a shared role for creating / deleting their resources for better permission control (Permission is no longer bound to the Lambda).
Also it is now possible to deploy static Next.js apps (without Lambdas).

Changelog

• Fixes deployments without Lambdas (#325)
• Use CloudFormation role (#324)
• Improve CLI (#323)
• Fix runtime bundle (#322)

v1.0.0-canary.2

This is the first preview release of atomic deployments.
Instead of serving just a single Next.js app from the module, it is now possible to serve multiple (unlimited) apps from the same CloudFront distribution.
Each deployment also gets a preview deployment that is assigned to a new subdomain.

Main changes

• Supports preview deployments (serves multiple deployments from the same CloudFront instance).
• New CLI actions (tf-next deploy, tf-next alias, tf-next deployment)

Changelog

Note: This is a complete rewrite of v1.0.0-canary.1, so don't expect a smooth upgrade.

• Adds static prefix to files served from S3 (#321)
• Add CLI commands (#317)
• No longer require reserved concurrency (#319, #251)
• Use CLI and CDK for deployments (#300)

v0.13.2

This is a bugfix release that fixes a regression in the tf-next build command.

Changelog

• Fixes a regression from the 0.13.1 release, where the @vercel/nft was not available (#322)

v0.13.1

This release brings support for pnpm based builds.

Changelog

• Update @vercel/nft from 0.10.0 to 0.19.1 (#320)

v0.13.0

Maintenance release that adds support for the nodejs16.x Lambda runtime.

Changelog

• Adds support for nodejs16.x runtime (#318, #316, #315)
• Increases minimum required Terraform AWS provider version from 4.8 to 4.15.0

v0.12.2

Changes

• Redirects now append the querystring from the original request
  When a request /oldLocation?foo=bar has a querystring, the params are now appended to the Location header:
  Location: /newLocation?foo=bar.
• Redirects are no longer cached by CloudFront
  All redirects issued by the proxy module use Cache-Control: public, max-age=0, must-revalidate now.
  It was Cache-Control: public, max-age=31536000, immutable previously.
  This mimics the same behaviour as how Vercel handles it.
• Redirects now issue a response
  Previously redirects had no content, now a plaintext response is returned, e.g. Redirecting to /newLocation?foo=bar (308).

Changelog

• Append querystring to redirects (#296, #304)

v0.12.1

This release fixes an issue where the following next/image settings from next.config.js were not passed correctly to the image optimization API.

• images.formats
• images.dangerouslyAllowSVG
• images.contentSecurityPolicy

Using one of these settings had therefore no impact on the optimization previously.

To update to the fixed version, both, the tf-next npm package and the Terraform module must be updated.

Changelog

• Pass image settings to the optimization module (#297, #299)

v0.12.0

Breaking changes

• The module now requires AWS Provider Version v4.8.0 or higher.
  Please follow the official upgrade guide when upgrading from the v3 provider: Terraform AWS Provider Version 4 Upgrade Guide.

• Attaching additional policies to Lambda role now requires second variable
  When using lambda_policy_json to attach additional policy statements to the Lambda role, you also need to set lambda_attach_policy_json = true now, otherwise the statements are ignored:

  module "tf_next" {
    source = "milliHQ/next-js/aws"
    ...
    
  + lambda_attach_policy_json = true
    lambda_policy_json        = ...
  }

Changelog

• Ensure compatibility with AWS Provider Version 4 (#286, #291)
• Add switch for attaching additional policy documents (#276)

New Contributors

• @christophebeling made their first contribution in #276