Fix release process, handle data assets correctly, rm old favicons #353
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://www.pivotaltracker.com/story/show/187028887
This PR removes the CopyWebpackPlugin, as this approach has never worked correctly with the new release mechanism. Things worked fine until we tried to update one of these images. So, from now on, the preset images are loaded using webpack. I've also removed some old favicon configurations and metadata, as it doesn't seem we set them that way in any other project. If we want to be really particular about favicons, there are webpack plugins that can generate everything for us.