0.2.4

What's Changed

Adds content comparison mitigation.

When converting an entityID, if the following conditions are met:

• The entity is a scene
• The previous hash exists using the pointer-changes API, which we can identify comparing by base-pointer.
• The previous deploy was less than 500 scenes away (since this is the limit I can query to pointer-changes)
• The manifest of the previous hash exists
• The version of the manifest of the previous hash is equal to the one that is being requested
• All of the files to be converted are present in the old manifest
• All the files in S3 from the previous manifest exists and are downloadable

If all of that checks out, we grab the previous assets instead of reconverting everything.

If the scene code changes, it doesn’t reconvert everything, but just moves files in S3.

If contents do not match, everything will be reconverted even by just one file.

Commits:

• fix: add version and environemnt control to file changes by @dalkia in #168
• fix: Better logging for HasContentChanged by @dalkia in #169
• fix: Create Output folder for HasContentChanged by @dalkia in #170
• fix: Add has content changed to log check by @dalkia in #172

Full Changelog: 0.2.3...0.2.4