Skip to content

Releases: lalalilo/aws-spa

v3.0.3

29 Sep 13:44
00a9ebe
Compare
Choose a tag to compare

3.0.3 (2021-09-29)

Bug Fixes

  • package.json & yarn.lock to reduce vulnerabilities (61edd1b)

v3.0.2

17 Mar 10:10
Compare
Choose a tag to compare

3.0.2 (2020-03-17)

Bug Fixes

  • 🐛 fix handling of /index.html (409adf6)

v3.0.1

12 Mar 08:27
7e030e6
Compare
Choose a tag to compare

3.0.1 (2020-03-12)

Bug Fixes

  • 🐛 fix cache invalidation not working when deploying with a path (ad3d0d4)

3.0.0

13 Dec 10:33
Compare
Choose a tag to compare

The behavior is unchanged on CI environments where the CI env variable is set (this is the case of most CI services such as Travis and CircleCI).

If you deploy from an environment where CI env variable is not set, you'll be prompt a confirmation message before deploying. You can remove this message thanks to the option --noPrompt

image

2.0.0

15 Nov 16:24
Compare
Choose a tag to compare

Add options to specify cache behavior: cacheInvalidation and cacheBustedPrefix.
There is a change in the behavior when not specifying these options:

  • cacheInvalidation: was implicitly set to index.html. Now its default value is *
  • cacheBustedPrefix: was implicitly set to static/. Now its default value is undefined (no cache busted folder)

To get the exact same behavior you must change:

- aws-spa deploy app.example.com
+ aws-spa deploy app.example.com --cacheInvalidation "/index.html" --cacheBustedPrefix "static/"

Write the code change above only if you use create-react-app.

1.6.0

12 Nov 07:27
Compare
Choose a tag to compare

✨ Introducing basic auth to avoid non-production apps to be indexed.

1.5.1

02 Nov 09:31
4a61aa7
Compare
Choose a tag to compare

Fix error "The specified bucket does not exist" on first deploy while adding public read to the bucket.

it seems to be due to some aws s3 async task while creating a bucket because it seems that we are correctly waiting for each HTTP request to be done before launching the next one.

1.5.0

01 Aug 07:25
Compare
Choose a tag to compare

Fixes:

  • ACM certificate creation now waits for certificate creation.

Improvements:

  • ACM certificate creation is now fully automated thanks to DNS validation
  • It is now possible to deploy on root domain